VMware Cloud Community
RajuVCP
Hot Shot
Hot Shot

Cannot executeupgrade script on host while upgrading esxi 5.1 to esxi 5.5 from update manager

Hi All,

Am getting the error message " cannot execute upgrade script on host"

while i was upgrading from esxi 5.1 to esxi 5.5 , i have googled similar issue was faced by many , and few did by uninstalling HA agent..

Does any one got the correct solution to resolve it.

Raju Gunnal VCP 4, VCP 5, VTSP 4, VTSP 5, ITIL V3 http://www.techtosolution.com
Tags (4)
10 Replies
vNEX
Expert
Expert

HI,

have you tried this solution:

VMware KB: Upgrading a VMware ESXi host fails with the error: Cannot run upgrade script on host

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Reply
0 Kudos
RajuVCP
Hot Shot
Hot Shot

I tried the steps given in above link, but it didnt worked for me..

Does any one tried other steps and resolved it?

Raju Gunnal VCP 4, VCP 5, VTSP 4, VTSP 5, ITIL V3 http://www.techtosolution.com
Reply
0 Kudos
vNEX
Expert
Expert

please post esxupdate.log  and vua.log  from /var/log ...

aslo check how much free space is on your host partitions with df -h


From which image was your ESXi 5.0 host previously installed? custom HP/Dell or standard VMware image? same applies for 3-rd party drivers...?

Have you seen some warnings in Remediation Wizard regarding 3-rd party software?


In the meantime (before post above logs) remove host from cluster reboot it detach/attach VUM baseline scan and try to remediate again.




_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
RajuVCP
Hot Shot
Hot Shot

Thanks for your reply,

Please find attached esxupdate.log and vua.log files.

i have checked the host have enough space.

~ # df -h

Filesystem    Size   Used Available Use% Mounted on

VMFS-5     1023.8G 301.1G    722.6G  29% /vmfs/volumes/ABC_S_001

VMFS-5     1023.8G 494.4G    529.4G  48% /vmfs/volumes/ABC_S_002

VMFS-5     1023.8G 395.5G    628.2G  39% /vmfs/volumes/ABC_S1_002

VMFS-5      267.2G  21.1G    246.1G   8% /vmfs/volumes/ABCDEF-local-storage

VMFS-5     1023.8G  48.5G    975.2G   5% /vmfs/volumes/ABC_S1_004

VMFS-5     1023.8G 257.1G    766.7G  25% /vmfs/volumes/ABC_S1_003

VMFS-5     1023.8G 356.1G    667.7G  35% /vmfs/volumes/ABC_S1_001

VMFS-5     1023.8G  26.8G    996.9G   3% /vmfs/volumes/ABC_V_002

VMFS-5     1023.8G 976.0M   1022.8G   0% /vmfs/volumes/ABC_V_001

vfat          4.0G  31.9M      4.0G   1% /vmfs/volumes/525c21a8-06675596-b24d-00                                                                             26b9625f7c

vfat        249.7M 161.3M     88.5M  65% /vmfs/volumes/76468f7b-08e231a6-02fc-7a                                                                             5b301aef7e

vfat        249.7M 145.8M    103.9M  58% /vmfs/volumes/6c0c1a76-1a931574-8e42-fd                                                                             ee9fba9337

vfat        285.8M 128.0K    285.7M   0% /vmfs/volumes/525c218f-0a03300c-c0f5-00                                                                             26b9625f7c

My esxisting esxi version is ESXi 5.1.0,  2000251 , its a custom image installed on Dell PowerEdge R710.

I have'nt seen any kind of 3rd party software warning message while remediating.

I have tried in first stoke(found on goodle) removed the host from cluster , rebooted  , detached and attached but that too didnt helped.

Raju Gunnal VCP 4, VCP 5, VTSP 4, VTSP 5, ITIL V3 http://www.techtosolution.com
Reply
0 Kudos
vNEX
Expert
Expert

Hi Raju,

vua.log shows that VUM is trying to upgrade your host via script that initiates an old esxupdate syntax which throws an error. That lead me to ask a question what version of VUM you have because only VUM 5.5 can upgrade 5.x hosts to 5.5...

Second question your 5.1 hosts were originally at which version when they were deployed for the first time?

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Reply
0 Kudos
RajuVCP
Hot Shot
Hot Shot

Am using update manager (VUM) 5.5.0.22432 version.

My esxi 5.1 host was installed with fresh esxi 5.1 ISO, in my organization till now whenever there is need for esxi upgrade , we use will install it with custom iso instead of upgrading from update manager.

These is the first time we are trying to upgrade from VUM. So the existing one host 5.1 is fresh install.


Raju Gunnal VCP 4, VCP 5, VTSP 4, VTSP 5, ITIL V3 http://www.techtosolution.com
Reply
0 Kudos
vNEX
Expert
Expert

Yes interactive upgrade is always an option but its bit painful if you have 10+ hosts...

back to the and of vua.log there is a warning:

WARNING:root:Couldnt load esximage database: Cannot merge VIBs Dell_bootbank_OpenManage_7.4-0000, Dell_bootbank_OpenManage_7.4-0000 with unequal filelist attributes

So I would recommend  try to locate and remove this VIB by:

esxcli software vib list

esxcli software vib remove -n <VIB name>

reboot and try to remediate host again...

If above steps doesn't help try to perform full  VUM reinstallation see more in this thread:

https://communities.vmware.com/message/1880437

If you do not want perform full VUM reinstall another option is to reinitialize VUM database !(This will completely erase VUM database inculding existing baselines)

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2...

Besides above I have additional questions:

what ISO image have you uploaded to VUM custom or standard iso image...(post link)?

Are you using Dell Open Manage?

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Reply
0 Kudos
vervoortjurgen
Hot Shot
Hot Shot

i had the same issue last week

in my case i had to uninstall the vshield from the host and put it in maintenance mode

then removed the host from cluster

lucky i had only 3 esx host in that config

kind regards Vervoort Jurgen VCP6-DCV, VCP-cloud http://www.vdssystems.be
Reply
0 Kudos
RajuVCP
Hot Shot
Hot Shot

Finally it solved for me. I executed below given commands.Removed the FDM agent on the host and rebooted.

cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp

chmod +x /tmp/VMware-fdm-uninstall.sh

/tmp/VMware-fdm-uninstall.sh

Reboot the host.

Start upgrading the esxi. It worked for me. Smiley Happy

Raju Gunnal VCP 4, VCP 5, VTSP 4, VTSP 5, ITIL V3 http://www.techtosolution.com
tjurgens
Enthusiast
Enthusiast

I second that fix.  Called VMware, they pointed me to this blog:

https://www.opvizor.com/blog/issues-upgrading-esxi-5-1-5-5/

I didn't see any VMware KB about this though.

My steps (functionally the same, however, slightly different commands):


cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp

chmod +x /tmp/VMware-fdm-uninstall.sh

cd /tmp

./VMware-fdm-uninstall.sh

I found that the last step can take a while, or seemingly hang.  I had to ctrl-c to get back to the prompt (after waiting 15 minutes) and when I ran the last line again it ran almost instantly.  After a reboot, I was able to proceed with the upgrade.

As a note - I did not have to uninstall the vShield agent to get the upgrade completed.