OPERATIONAL DEFECT DATABASE
...
...
Document VersionRelease DateDetails207/08/2019Updated Resolution with permanent fix, firmware version 3.0.542.109/25/2018Original document releaseThe Smart Update Manager (SUM) may incorrectly report that an HPE Superdome Flex server firmware update was successful, approximately two minutes after deployment was started. The success status is incorrect and the firmware update is still ongoing. The incorrect successful update appears as follows:Warning: Do not reboot or AC-cycle the system as SUM may still be updating the system. Doing so may corrupt firmware beyond recovery. Upon successful completion of the firmware update, the RMC/eRMC and BMC will automatically reboot to activate the new firmware.HPE recommends always verifying that firmware update has completed successfully before booting the system or taking any actions. To check on status of a SUM firmware update after SUM reports success, perform the following steps:Check the SUM log. If the "Log Date" and "Log Session End" time difference is five minutes or less, wait at least 20 minutes, then proceed to next step. To view the SUM log, click on the "View Log" button at the bottom of the page, then "View log" on the right side of the dialog box:The suspicious SUM log looks like this:====== Smart Update Manager Installation Log ======Source: firmware-sdflex-2.5.256-1.1.i586.rpmVersion: 2.5.256Log Date: 9/11/18 12:48 PMStarting update with binary file sd-flex-2.5.256-fw.tarsInitiating UpdateAll actionUpdateAll action initiated successfullyUpdate in progress..........Update completed successfullyThe operation was successful.------------------------------------------------------------------End Session-----------------------------------------------------------------Setup utility completed.Log Session End. [12:49:16]Return Code (0)======================================================For comparison, a correctly successful SUM log looks like this. Note the longer progress indications and system reboot report:====== Smart Update Manager Installation Log ======Source: firmware-sdflex-2.5.256-1.1.i586.rpmVersion: 2.5.256Log Date: 9/13/18 5:05 PMStarting update with binary file sd-flex-2.5.256-fw.tarsInitiating UpdateAll actionUpdateAll action initiated successfullyUpdate in progress..........................................................................................................................System rebooting...........System rebooting...........System rebooting...........System rebooting...........System not reachable, reboot possibly in progress. Retrying to check update status...System rebooting...........Update completed successfullyThe operation was successful.------------------------------------------------------------- End Session------------------------------------------------------------Setup utility completed.Log Session End. [17:16:29]Return Code (0)======================================================2. ssh to the RMC/eRMC and log in as administrator, using the password specific to the system. If ssh times out, or if you cannot login as administrator, wait at least one minute and retry. If you are unable to ssh to the RMC/eRMC after ten tries, contact HPE support for help.3. Run SHOW FIRMWARE VERBOSE and check the output. If the "Configured version" matches the version in SUM Baseline and that CLI reports "Firmware on all devices matches the configured version," SUM has successfully updated the system and the system is ready for use.4. If the Configured version does not match the version deployed by SUM, or if CLI reports any mismatches:Disconnect from the ssh session.Wait five minutes.Repeat steps 2 and 3.If the firmware version shows any mismatches after 3 repeated attempts, contact HPE support for help.
Any HPE Superdome Flex server in which an HPE SUM firmware update is being performed.
This issue is corrected in firmware version 3.0.542:https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_b71ab9b3511b46e9bd998af2d0The most likely cause for an incorrect success report is the use of HTTP and HTTPS proxies on the host running SUM. As a workaround, HPE recommends that you clear proxy settings before launching SUM.On a Linux system:1. Open a terminal to launch SUM. The rest of these instructions assumes you are using bash as your shell. If not, substitute the equivalent commands for your shell.2. Execute the following commands:unset http_proxyunset HTTP_PROXYunset https_proxyunset HTTPS_PROXYcd /<path_to_SUM>./smartupdate3. The browser window will appear. Use the browser setup menu to select no proxy. For example, if you use FireFox, select the menu on the right, then Preferences, then Advanced, then Network, then Settings, then click on "No proxy."4. Run SUM normallyOn Windows systems:Assuming your default browser is Internet Explorer (IE):1. Open IE, use the menu to bring up Internet Options. Click on Connections tab, then LAN settings.2. Make sure that both "Automatically detect settings" and "Use automatic configuration script" are not set:3. Open Windows Explorer and navigate to the SUM folder.4. Double-click on smartupdate.bat file.5. The IE window will soon appear.6. Run SUM normallyNOTE:Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.RECEIVE PROACTIVE UPDATES: Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL:Proactive Updates Subscription Form.NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to theNavigation Tips document.SEARCH TIP: For hints on locating similar documents on HPE.com, refer to theSearch Tips Document.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
