Please follow ‘HOW TO: Upgrade EMC UIM/P‘ blog post for instructions how to upgrade UIM/P.
When performing UIM/P upgrade from version 4.0 to 4.1 it may fail with the following error message:
Last Install: Failed to install updates (Error while running pre-install scripts)
If you check /opt/ionix-uim/logs/appliance-update.log you will see the following:
Version – 4.0.0.2.359
Description –
Unified Infrastructure Manager/Provisioning
04/06/2014 11:31:19 9440 main:UA_CLI.cpp:187 (updatecli) [INFO] Starting Install 04/06/2014 11:31:19 9440 updateStatus:UA_CLI.cpp:45 (updatecli) [INFO] Update status: Starting Install 04/06/2014 11:31:19 9440 updateStatus:UA_CLI.cpp:45 (updatecli) [INFO] Update status: Running pre-install scripts 04/06/2014 11:31:19 9440 executeFile:UA_CLI.cpp:86 (updatecli) [INFO] Running /opt/vmware/var/lib/vami/update/data/job/8/pre_install '4.0.0.359' '4.1.0.598' Installing update from version 4.0.0.359 to version 4.1.0.598 Checking the vendorUUI ... Checking the productRID ... Checking vendorUUID and productRID completed successfully... Vami needs to be updated. Run the following commands: cd /opt/ADG/adg_vami25 ./InstallVami25Package.sh 04/06/2014 11:31:20 9440 executeFile:UA_CLI.cpp:92 (updatecli) [ERROR] Failed with exit code 256 04/06/2014 11:31:20 9440 updateStatus:UA_CLI.cpp:45 (updatecli) [INFO] Update status: Running post-install scripts 04/06/2014 11:31:20 9440 executeFile:UA_CLI.cpp:86 (updatecli) [INFO] Running /opt/vmware/var/lib/vami/update/data/job/8/post_install '4.0.0.359' '4.1.0.598' 1 Failed with status of 1 while installing version 4.1.0.598 VM version is still 4.0.0.359
It clearly says that VMware Studio Virtual Appliance Management Infrastructure (VAMI) needs to be updated to version 2.5.
To update VMware Studio VAMI:
- go to
/opt/ADG/adg_vami25 - and execute install script:
UIM-DC1:/opt/ADG/adg_vami25 #
./InstallVami25Package.sh
---------------------------------------
Checking the current vami version before update
Creating logfile: /opt/vmware/var/log/vami/InstallVami25Package.log
Checking the 2.1 vami packages
Checking the 2.5 vami packages
Checking the file: vami_ovf_process
Un-install the old vami packages:
Install the new 2.5 vami packages:
insserv: can not stat(emc-homebase-serverdb)
insserv: can not stat(emc-homebase-server)
insserv: can not stat(emc-homebase-serverdb)
insserv: can not stat(emc-homebase-server)
/opt/vmware/bin/sfcbrepos: line 182: 9572 Segmentation fault (core dumped) sfcbinst2mof -n $namespace -c $instfile -o $instmigfile -r $registrationdir/repository.previous/ -g ${DESTDIR}/opt/vmware/etc/sfcb/sfcb.cfg 2> /dev/null
/opt/vmware/bin/sfcbrepos: line 182: 9573 Segmentation fault (core dumped) sfcbinst2mof -n $namespace -c $instfile -o $instmigfile -r $registrationdir/repository.previous/ -g ${DESTDIR}/opt/vmware/etc/sfcb/sfcb.cfg 2> /dev/null
Replace the file: vami_ovf_process
Adding vami group
Start up the 2.5 vami vami-fscb services
Start up the 2.5 vami vami-lighttp services
vami package updated successfully
Go back to the upgrade page and start again. This time the upgrade should finish successfully.
Excellent post, Ziggy, as always!
This must be one of these occasions when we actually need to RTFM!!! :) The procedure is documented in the Read Me file on page 8. :)
Well, I got cough by this as well! :)
lol, nobody reads this :)))
People do read this, Thanks Ziggy, useful as always…
Seconded! People do read this! Thanks Ziggy!
why does it not just do that as part of the upgrade?
God knows! Some of the error messages could be more informative!…