The following are known issues present in the current release of iLOrest. If available, a link to the relevant Customer Advisory (CA) has been included:
| Issue | CA | Description | Workaround |
|---|---|---|---|
Rawget fails with error: ERROR : Failed to detect iLO version prior to responding with the desired output. | NA | The command returns the error when Out-of-Band requests are sent from a Virtual Machine (VM). | Send iLOrest rawget requests from an OS hosted by a physical system. |
| ilorest login --url <iLO_IP> -u <username> -p <password> fails when run from ESXi (esxcli). | NA | Detection of iLO version is not succeeding in esxcli ilorest commands. | Use ilorest.sh from the iLORest installation on a supported OS (Linux or Windows) rather than using esxcli commands. |
iLOrest commands when executed with PyPI version of the tool, throws the error code 255 upon any failure. | NA | When the iLOrest commands are run from PyPI installation , even if there is specific error code, ilorest displays 255 generic error code. | None. Please note that the functionality is not impacted; however, the actual error code is not currently displayed. |
| iLOrest uninstallation deletes the application accounts. | NA | When ilorest application is upgraded or uninstalled the existing application accounts are deleted. | Customer can re-create the application accounts either from iLO Web-UI or from iLOrest (Appaccount). |
flashfwpkg command is unable to wait until the PLDM component HPE_UBM7_1.10_B.fwpkg is flashed. | NA | The command fails as the timeout is hit , instead of waiting for the component to flash. | Customers can upload the component to ilo repository followed by creating and invoking the install set for this component. |
flashfwpkg command is unable to flash multiple drives connected behind a storage controller. | NA | When several drives are connected to the same controller, the update can only proceed if all selected drives are ready for the update. | |
| If even one drive is not eligible for the update (for example, because it has a problem or does not support the selected firmware), the system stops the update and rejects the request. | iLO GUI can be used to flash it directly. | ||
flashfwpkg command shows a warning on stdout despite successful flash. | NA | The command shows a warning message on stdout even when the flash operation is successful. | Verify the firmware version. If updated, the warning can be ignored. See iLORest Error and Warning Codes documentation for details. |
flashfwpkg command should not flash when iLO is enabled with TPM and --tpmover option not provided. | NA | The command does not prevent flashing when TPM is enabled in iLO and the --tpmover flag is not specified. | None. Use the -v option to view error code and diagnostic information; note that it does not prevent or stop the firmware flashing process. |
flashfwpkg command flashes firmware of drives behind a controller without --tpmover. | NA | The command flashes firmware of drives connected behind a controller even when the --tpmover flag is not specified. | Use iLO GUI and check the TPM Override checkbox. |
| IP 4.32 fails to download AHS logs from certain ProLiant models. | NA | Integrated Platform (IP) version 4.32 fails to download Active Health System (AHS) logs from certain HPE ProLiant server models. | Use IP 4.31.4 with iLOrest 4.6.0.0. |
--ilossa option in serverclone is unsupported for HPE iLO 5. | NA | The --ilossa option for smart storage array cloning is not supported on HPE iLO 5 based servers. | Use createvolume to create volumes. |
| Certificate login in ESXi 7.0 does not work. | NA | Certificate-based authentication does not function properly when using ESXi 7.0. | • Last column: Replace "remote login" with: "remote (out-of-band) certificate login |
Directory group clone in serverclone does not work. serverclone --source <source_server> --target <target_server> does not clone directory groups | NA | Directory group (LDAP) configurations are not included in serverclone operations | Use iLORest directory group management commands (list, create, delete). See iLORest Directory Group Management documentation. |
| iLOrest exits during UBM3 Backplane Firmware Update, but update continues. | a00134171en_us | When running a UBM3 (Universal Backplane Management 3) Backplane firmware update using iLORest in in‑band mode (for example, iLORest executed on the host OS), the iLORest application may exit unexpectedly. Although the CLI exits, the firmware update continues running in the background and can complete successfully. | Use iLO web interface or remote mode from another system to update firmware. |
| Attribute error when setting static IP on DHCP-configured iLO. ilorest load network.json --url <iLO_IP> -u <username> -p <password> | NA | When using the load command to set a static IP on an iLO configured for DHCP, iLORest returns an attribute error because the network properties are not writable in DHCP mode, and the configuration change is not applied. | Use rawpatch instead of load. |
| TLS 1.2 + EMS unsupported with ESXi 7.0 OS. | NA | When running iLORest on ESXi 7.0, the External Management Service (EMS) does not support the TLS 1.2 configuration required by iLO. Because iLORest depends on the OS TLS stack for secure communication, connections to iLO are not supported in this configuration. | Upgrade to ESXi 8.0. |