Updating the HMC from v7.7.8.0 to v7.7.8.0 SP1 was once again and like the previous HMC Update to 7.7.6.0 SP1 and HMC Update to 7.7.7.0 SP2 very painless. The service pack MH01397 was easily installable from the ISO images via the HMC GUI.
The service pack and the additional efixes showed the following output during the update process:
MH01397:
Management console corrective service installation in progress. Please wait... Corrective service file offload from remote server in progress... The corrective service file offload was successful. Continuing with HMC service installation... Verifying Certificate Information Authenticating Install Packages Installing Packages --- Installing ptf-req .... --- Installing RSCT .... src-3.1.4.9-13275 rsct.core.utils-3.1.4.9-13275 rsct.core-3.1.4.9-13275 rsct.service-3.5.0.0-1 rsct.basic-3.1.4.9-13275 --- Installing CSM .... csm.core-1.7.1.20-1 csm.deploy-1.7.1.20-1 csm_hmc.server-1.7.1.20-1 csm_hmc.hdwr_svr-7.0-3.4.0 csm_hmc.client-1.7.1.20-1 csm.server.hsc-1.7.1.20-1 --- Installing LPARCMD .... hsc.lparcmd-3.3.0.1-1 ln: creating symbolic link `/usr/hmcrbin/lsnodeid': File exists ln: creating symbolic link `/usr/hmcrbin/lsrsrc-api' : File exists ln: creating symbolic link `/usr/hmcrbin/mkrsrc-api' : File exists ln: creating symbolic link `/usr/hmcrbin/rmrsrc-api' : File exists --- Installing InventoryScout .... --- Installing Pegasus .... --- Updating baseOS .... cp: cannot stat `.dev': No such file or directory cp: cannot stat `.image.updates': No such file or directory PreInstalling HMC REST Web Services ... Installing HMC REST Web Services ... /dump/hsc_install.images/images/./installK2Payloads.sh: line 84: K2Payloads.txt: No such file or directory Corrective service installation was successful.
MH01416:
Management console corrective service installation in progress. Please wait... Corrective service file offload from remote server in progress... The corrective service file offload was successful. Continuing with HMC service installation... Verifying Certificate Information Authenticating Install Packages Installing Packages --- Installing ptf-req .... Corrective service installation was successful.
MH01423:
Management console corrective service installation in progress. Please wait... Corrective service file offload from remote server in progress... The corrective service file offload was successful. Continuing with HMC service installation... Verifying Certificate Information Authenticating Install Packages Installing Packages --- Installing ptf-req .... Verifying archive integrity... All good. Uncompressing Updating from 2014-02-17 to 2014-04-08. ................................................................................................... ......................................................................................................................... ... .. ........ .. .. .. .. .. ........ ... .. .. .. .. ........ .. .. ... . ... . .. .. . ......... . . . . . Updating to hmc61_1-mcp-2014-04-08-203505... upgrading distro_id... Preparing... ################################################## distro_id ######### ################################### # # ## ## Preparing... ########## ########## ########## ########## ########## openssl # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ###### # binutils_static # # # # # # # # # # # ### # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # distro_id ######### ################################## # # ### ## openssl-fips ## # ##### ###### ###### ##### ###### ###### ###### ##### ## Updating distribution id... Updating manifest... Corrective service installation was successful.
The MH01397 update still shows error messages with regard to symlink creation appearing during the update process, which can be savely ignored. The error message “cp: cannot stat `.dev': No such file or directory” is also becoming an old friend and originates from the shell script /images/installImages inside the MH01397 installation ISO image, where non-existing files are attempted to be copied. The newly introduced error message “cp: cannot stat `.image.updates': No such file or directory” falls into the same category.
The error message “/dump/hsc_install.images/images/./installK2Payloads.sh: line 84: K2Payloads.txt: No such file or directory” seems to be more serious. From tracing down the call order of /images/installImages inside the MH01397 installation ISO image:
448 449 if [ -f $image/installK2Payloads.sh ] 450 then 451 echo "Installing HMC REST Web Services ..." 452 $image/./installK2Payloads.sh $image 453 fi 454
to:
4 5 LogFile=/tmp/K2Install.log 6 IndexFile=K2Payloads.txt 7 [...] 68 69 # Install the K2 rpms if K2 directory exists 70 if [ -d $image/K2 ]; then 71 cd $image/K2 72 73 while read line 74 do 75 rpmToInstall=`echo $line | cut -d '/' -f 4` 76 rpmToUpdate=`echo $line | cut -d '/' -f 4 | cut -d '-' -f 1` 77 /bin/rpm -q $rpmToUpdate 78 if [ $? -eq 0 ]; then 79 /bin/rpm -vvh -U $rpmToInstall >> $LogFile 2>&1 80 else 81 /bin/rpm -vv -i $rpmToInstall >> $LogFile 2>&1 82 fi 83 done < $IndexFile 84 fi 85
it seems the file K2Payloads.txt is missing from the “K2” directory containing the RPM files for the HMC REST web services:
$ mount -o loop HMC_Update_V7R780_SP1.iso /mnt $ ls -al /mnt/images/K2/ total 251394 dr-xr-xr-x 2 root root 4096 Mar 5 19:57 . dr-xr-xr-x 8 root root 2048 Mar 5 19:57 .. -r--r--r-- 1 root root 30 Feb 18 03:52 k2.version -r--r--r-- 1 root root 13398 Feb 18 04:12 pmc.core-7.7.8.1-20140217T2012.i386.rpm -r--r--r-- 1 root root 14242627 Feb 18 04:00 pmc.pcm.rest-7.7.8.1-20140217T2019.i386.rpm -r--r--r-- 1 root root 33865936 Feb 18 03:58 pmc.soliddb-7.7.8.1-20140217T2012.i386.rpm -r--r--r-- 1 root root 15375 Feb 18 04:01 pmc.soliddb.pcm.sql-7.7.8.1-20140217T2020.i386.rpm -r--r--r-- 1 root root 46559 Feb 18 04:10 pmc.soliddb.rest.sql-7.7.8.1-20140217T2019.i386.rpm -r--r--r-- 1 root root 54565876 Feb 18 03:59 pmc.ui.developer-7.7.8.1-20140217T2021.i386.rpm -r--r--r-- 1 root root 74508025 Feb 18 03:57 pmc.war.rest-7.7.8.1-20140217T2013.i386.rpm -r--r--r-- 1 root root 76751466 Feb 18 03:58 pmc.wlp-7.7.8.1-20140217T2012.i386.rpm -r--r--r-- 1 root root 478438 Feb 18 04:08 pmc.wlp.commons-7.7.8.1-20140217T2013.i386.rpm -r--r--r-- 1 root root 1695200 Feb 18 04:08 pmc.wlp.guava-7.7.8.1-20140217T2019.i386.rpm -r--r--r-- 1 root root 109789 Feb 18 04:09 pmc.wlp.jaxb2.runtime-7.7.8.1-20140217T2019.i386.rpm -r--r--r-- 1 root root 446974 Feb 18 04:08 pmc.wlp.log4j-7.7.8.1-20140217T2019.i386.rpm -r--r--r-- 1 root root 428041 Feb 18 04:09 pmc.wlp.quartz-7.7.8.1-20140217T2020.i386.rpm -r--r--r-- 1 root root 29861 Feb 18 04:09 pmc.wlp.slf4j.api-7.7.8.1-20140217T2013.i386.rpm -r--r--r-- 1 root root 219413 Feb 18 03:58 pmc.wlp.soliddriver-7.7.8.1-20140217T2012.i386.rpm
Without privileged access to the HMCs OS its hard to verify, but it appears that the updates to the HMC REST web services have not been installed. So i guess i'll be opening up a PMR about that now.
The weird “.” and “#” characters in the output of the MH01423 update can also savely be ignored. They're just unhandled output from the update script and the RPM commands called therein. To take a look for yourself:
$ mkdir /tmp/hmc && cd /tmp/hmc $ mount -o loop MH01423.iso /mnt $ /mnt/images/update-hmc61_1-20140217-20140408.sh --tar xvf $ ls -al total 4100 drwxr-xr-x 3 root root 4096 Apr 26 23:07 . drwxrwxrwt 35 root root 24576 Apr 26 23:07 .. -rw-rw-r-- 1 root root 2524328 Jun 19 2010 binutils_static-2.20.0-21.i686.rpm drwxr-xr-x 2 root root 20480 Apr 9 17:48 DEPENDS -rw-rw-r-- 1 root root 24564 Aug 23 2012 distro_id-1.0-9.i686.rpm -rwxr-xr-x 1 root root 56125 Apr 9 17:49 hmc61_1-mcp-2014-04-08-203505-manifest.txt -rw-rw-r-- 1 root root 1316850 Apr 8 22:56 openssl-1.0.1e-20.i686.rpm -rw-rw-r-- 1 root root 198060 Apr 8 22:56 openssl-fips-1.0.1e-20.i686.rpm -rwxr-xr-x 1 root root 3462 Apr 9 17:49 setup.sh $ less setup.sh
In the file setup.sh look for the RPM install (“rpm -Uvh”) or update (“rpm -ivh”) calls being done explicitly with the verbose and hash option. This seems to be a bad choice, because the WebUI seems not to be able to handle the output produced by the RPM commands. Certainly not pretty to have that in the output of the update process, where it could be cause for some confusion. But in the wake of the OpenSSL heartbleed bug, which MH01423 addresses, a quick and dirty solution probably seemed more appropriate.
More importantly though, going through the HMC WebUI and checking for any differences and functional breakage, i stumpled upon a long missed feature that IBM apparently had already sneaked in with the previous HMC version 7.7.8.0: Sync current configuration Capability. And without me even noticing! Finally, no more bad surprises after a LPAR shutdown and re-activation!