SUT in AutoDeployReboot but server doesn't reboot

[BSTRD]

Doing online firmware + driver updates of windows servers via Oneview profile with new SPP.

The Profile is set to "Firmware and OS Drivers using Smart Update Tools" and activation is set to immidiately. Sut agent is set to polling interval 2min and is set to AutoDeployReboot mode.

All packages are staged to the server, ilo 2.8.1 + new bios is installed, and the process stalls here expecting a reboot for activation - which supposedly should happen automaticcally when running in ADR - except it doesnt.

I can see in the cfg-file that there is a parameter called REBOOTALLOWED but this is set to false despite the mode being ADR - but I cant find any documentation for manipulating this parameter?

/Morten

[denialr4545]

Hello,

It sounds like you're experiencing an issue with the automatic reboot during the firmware and driver update process via OneView profile with the new SPP.

Regarding the "REBOOTALLOWED" parameter, it is likely that this parameter is used by the OneView software to control the reboot behavior during the firmware and driver update process. However, manipulating this parameter may not be recommended, as it may cause unexpected behavior and potentially harm the server.

Instead, I would suggest checking the logs to see if there are any error messages or warnings that may indicate why the automatic reboot is not occurring as expected. You may also want to check if there are any settings or configurations within the server's BIOS or iLO that could be preventing the automatic reboot from occurring.

If you are still having trouble resolving the issue, you may want to contact the vendor's technical support team for further assistance. hope so it is useful for you.

[MV3]

Hello 

In any of the auto modes, iSUT runs as a service and polls the iLO for requested updates from SPP.

Once detected, iSUT performs the following actions allowed by the mode:
* Just stage the updates
* Stage and deploy
* Stage, deploy, and reboot
For AutoStage, you must still run <sut deploy> after staging is done for the updates to be installed, allowing the OS user to control when updates are performed.

Please raise a support case with HPE in case you are still facing difficulties even after running the <sut deploy>.

Cheers...

[BSTRD]

The mode is set to AutoDeployReboot, already tried manual deploy + activation but this is not valid input in cli when running in ADR and should not be necessary when running in ADR.

To me this is a clear issue with the rollout procedure used either from Oneview or the SPP sum used by Oneview (2023.03).

I have the same issue regardless of doing it on a windows or esxi host, on both Apollo 4200 G10 and DL380 G10/G10+ models. Offline application worx fine which is why I am off the oppinion that the error is probably in Oneview.

1) Profile update is initiated and all packages are staged to the server and are visible in the ilo queue.

2) Activation is started, ilo 2.81 is the first package - this gets deployed and activated (ilo is reset with the new firmware)

3) next package is server BIOS - this gets installed but not activated (server doesnt reset), the process waits indefinately at this point until a timeout-error in Oneview is triggered.

4) If I reboot the server manually the BIOS gets activated and after completing the reboot sequence the rollout + reset of all subsequent packages proceed and gets executed as expected when running in AutoDeployReboot mode.

5) Bitch about having to update 60+ servers when I have to monitor + boot each of them manually.

/Morten

[MV3]

Hello

Please raise a support with HPE for further review of the issue.

Cheers...

[Robert Eckdale]

It's my understanding that the AutoDeployReboot paramater, which I also have set on my ESXi hosts, will only restart the host if it is in maintenece mode. Presumably this is a 'safety' feature.. I can't speak to how this would behave on a non-ESXi hosts; I assume it just wont restart the host.