OneView 2.00.02-0219211 and 2016.04 SPP

[MatthewMcG]

I currently have a support case open and we are having issues deploying the 2016.04 SPP via OneView and SUT.  When deploying it the firmware install state gets stuck at "Installing" in OneView.  The only way to resolve this is to power off the sever, change the profile to manual, power up server, change back to SPP managed.  Upon further investigation a hpsut -status shows that the system update manager is " OS Administrator" instead of "HP OneView".  To date we have not experienced this issue using prior SPP versions.  Support has asked that I first update iLO to 2.40 (currently on 2.30 with Advanced License) before attempting again which has worked but now we are experiencing profile errors when trying to edit profiles which leads to powering down and reseating blades (BL460c Gen9).  What would cause the firmware install state to become stuck using the new SPP?

[JSmid]

We were running into these same problems and removing the profile and then reapplying also fixed it. For now we have stopped using the HP SUT tooling because of this.

[ChrisLynch]

Reassigning the Server Profile only will attempt to reactuate the HPSUT service.  If the HPSUT service is not operating correctly, then components will never be delivered.  Your iLO's need to be atleast 2.30 per the documentation.  It is advised customers upgrade their iLO's to 2.40 to address a number of iLO issues most have experienced with iLO 2.20 and 2.30.  Also, please make sure that if you attempt to scan a system with HPSUM, it will impact the operation of HPSUT.  HPSUT may fail to startup or even connect to the OneView appliance due to HPSUM residual binaries being present and still running.

[MatthewMcG]

Thanks for the information but we have no issues deploying previous SPPs.  All of our Gen8 and Gen9 Bl460c blades are already at 2.30 and I checked the servers that are stuck on "Installing" and saw no indication of the HPSUM service running.  It is just this SPP (2016.04) we are having trouble with.  I have found that the 2016.04 version has a newer version of SUM.  As a workaround i created a custom SPP based off 2015.10 version and added the 2016.04 packages excluding iLO 2.40 and this custom SPP works for us.  I should not have to update iLO before deploying a SPP that contains iLO firmware.  So far HPE support do not have an answer on why this is happening.  They have stated the logs indicate that there are communication issues between iLO 2.40 and OneView.  I hear that there are rumors of a July SPP being released.  Are you able to share information on that?

[MatthewMcG]

HPE Support has reported that they were able to reproduce the issue in their labs and are investigating.  I'll update when they get back to me

[AmitG0223]

So it seems like it is an issue with hpsum as I have the same issue with HPE OneView 2.00.07

[MatthewMcG]

After working with HPE support it turns out as i understand it is that the 2016.04 SPP contains iLO 2.40 that corrects errors in previous iLO versions.  After iLO 2.40 or later is applied it erases some data contained on server NVRAM that OneView reads from.  This effectively locks the profile with OneView v2.00.07-025853 with errors of network connectivity issues to iLO and various others. With previous versions it may get stuck at "installing" if using SUT.  The soluiton is reapply the profile after the hardware completes a full POST after iLO 2.40 or higher is applied...

1. apply iLO 2.40 or later (preferably v2.44)

2. reboot server (let it complete POST, does not have to go into OS you can hit F11 to get boot menu)

3. shutdown server and reapply profile by toggling the firmware managment option to manual. (this will rewrite the missing data to the NVRAM.)

4.  Power up server and reconfigure your profile as desired.

[AmitG0223]

I had encountered the same issue. The way I was able to get it working without the method you provided is

1. Export the HPSUT configuration (hpsut /exportconfig) it will display where it was exported to
2. Modify the config file to my needs
3. Rename hpsut/config/hpsut.cfg
4. Copy the new config file to hpsut/config/hpsut.cfg

I have tried this on both Windows and Linux upgrading to 2.40/2.42/2.44 and did not encounter the issue with this method.