redfishlib.cpp:264 :: In executeRedfishCall()
On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter, so a cluster image can carry the firmware as well.
On a current project we run vSphere Lifecycle Manager together with HPE OneView and HPE OneView for vCenter. Those components let us define a cluster image that includes the firmware.
Prerequisites
A few things have to be in place for these features:
- HPE OneView is installed
- The HPE SPP is registered in HPE OneView
- The server hardware is recorded in HPE OneView
- HPE OneView for vCenter is installed and configured
- The SPP is registered in vCenter
- The cluster image is configured, firmware components included
- The servers already have the vendor add-on installed (that is what brings the SUT tool)
- The servers have SUT configured in AutoDeploy mode
The problem
In one environment we could not stage or remediate a host. These errors kept showing up in the log:
[INFO] :: [redfishlib.cpp:264] :: In executeRedfishCall(), the operation is rawget the link is /redfish/v1/systems/1/hpserversettings/firmwaredriverbaselinesettings/
[ERROR] :: [redfishlib.cpp:352] :: Error value from Transaction is : -12 and error name is HTTP server returned error status.
[ERROR] :: [sutmetadatainterface.cpp:739] :: Unable to sync OV to HP Tools in RIS
We found them in /var/log/sut.log.
Troubleshooting steps
None of these solved it:
- Reboot the ESXi host
- Reboot HPE OneView
- Reboot HPE OneView for vCenter
- Reboot vCenter Server
- Reset the HPE iLO
The log messages stayed exactly the same and the host would not take the new firmware.
Solution
The remaining options would have been:
- Remove the HPE server from HPE OneView and add it again
- Reinstall ESXi on the HPE server
- Open an HPE support case
Removing the host from HPE OneView and adding it back made the errors disappear.
Solution: re-register the HPE server in HPE OneView.