HewlettPackard / PowerShell-ProLiant-SDK

PowerShell sample scripts for managing HPE servers
https://www.hpe.com/servers/powershell
90 stars 42 forks source link

Get-HPEILOHealthSummary with ILO5 Firmware 2.72 #81

Closed Michel-CO closed 1 year ago

Michel-CO commented 2 years ago

Hi, i test the new ILO5 firmware with some scripts from us. Now i found a strange error, when i use the command Get-HPEiLOHealthSummary (HPE-ILO Module Version 3.3.0.0):

[Get-HPEiLOHealthSummary : [iloFQDN]: Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'HPE.iLO.Communication.Redfish.DataEntity.OData' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly. To fix this error either change the JSON to a JSON object (e.g. {"name":"value"}) or change the deserialized type to an array or a type that implements a collection interface (e.g. ICollection, IList) like List that can be deserialized from a JSON array. JsonArrayAttribute can also be added to the type to force it to deserialize from a JSON array. Path 'Oem.Hpe.Links.PCIDevices', line 1, position 4909. At line:1 char:8

This error only show at new firmware ILO 2.72.

Can you reproduce and fix this?

JoMontel commented 2 years ago

You are not alone.

Get-HPEiLOHealthSummary : [x.x.x.x]: Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'HPE.iLO.Communication.Redfish.DataEntity.OData' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly. To fix this error either change the JSON to a JSON object (e.g. {"name":"value"}) or change the deserialized type to an array or a type that implements a collection interface (e.g. ICollection, IList) like List that can be deserialized from a JSON array. JsonArrayAttribute can also be added to the type to force it to deserialize from a JSON array. Path 'Oem.Hpe.Links.PCIDevices', line 1, position 5879. At C:\Scripts\BareMetalDeployment\05_MainScript\New_BareMetalSynergyServer_v3.4.ps1:119 char:15

This needs to be addressed, as it is preventing us from deploying ESX on a wide scale.

Lines used: $iloConnection = Connect-HPEiLO -IP $iLOIPaddress -Username $iloUsername -Password ($DecriptIloPassword).GetNetworkCredential().password -DisableCertificateAuthentication #-WarningAction SilentlyContinue -Verbose:$false -ErrorAction SilentlyContinue

$status = Get-HPEiLOHealthSummary -Connection $iloConnection -WarningAction SilentlyContinue #-ErrorAction SilentlyContinue -Verbose:$false

hp-powershell commented 1 year ago

hi ,

This issue is fixed in our upcoming release HPEiLOCmdlets 4.0 which is scheduled for Jan next year .

Thanks & Regards, Powershell Team

klaspihl commented 1 year ago

hi ,

This issue is fixed in our upcoming release HPEiLOCmdlets 4.0 which is scheduled for Jan next year .

Thanks & Regards, Powershell Team

@hp-powershell , Do you have a release date on version 4.0`?

Michel-CO commented 1 year ago

HPE released the new CMDLets: https://support.hpe.com/connect/s/softwaredetails?language=de&softwareId=MTX_bb648dcdf9b9424b8ffdd96d53