amirzadeh
Contributor
Contributor

Update of VMSA 7.0.1 is stuck at 92% - Converting data as part of post install

Jump to solution

I had an "urgent" update for my appliance so I went to vSphere manager and started the update and everything was going fine until it got stuck at 92%.

I tried restarting the VM after the instance comes back online (no matter what URL you go to) you end up on the converting screen and it's still sitting at 92%.

Any help would be greatly appreciated.

[ I do have a Snapshot of the VM, and VMSA backup available ]

0 Kudos
1 Solution

Accepted Solutions
VMAKS
VMware Employee
VMware Employee

@amirzadeh

Thank you for the update.
Before patching VCSA please take a back of the vCenter and take a non-memory, non-quiesced snapshot of the vCenter VM(and PSC if it is external), before implementing any change.
Ensure that you have the login credential for the ESXi host which has the vCenter VM.

Then you can download the VCSA patch which should end with FP.iso from my.vmware.com > selecting VC and the version.
Upload the file to a datastore and map it to the VCSA VM through CD / DVD Drive option.
Patch the VCSA from CLI.

Run the following commands

software-packages stage –-iso

software-packages list –-staged

software-packages install –-staged

Reboot the VCSA VM.

This should patch the VCSA

 

Arun Kumar

Install / Upgrade

View solution in original post

0 Kudos
3 Replies
VMAKS
VMware Employee
VMware Employee

@amirzadeh

 

Thank you for posting on VMware Communities.

 

Regarding "Update of VMSA 7.0.1 is stuck at 92%", are you referring to vCenter Server Appliance VCSA or VMware Security Advisory VMSA ?

Once this is sorted out we can move ahead with the query.

 

Thank you,

 

Regards,

Arun Kumar

Install / Upgrade

 
0 Kudos
amirzadeh
Contributor
Contributor

VMCA appliance.. but the post is now moot.  I deleted the instance, re-installed and tried to restore from backup but then it wouldn't let me actually restore because I had no resource pools assigned (which seems to be a DRS? feature) which I don't have.

I finally just imported the DS and VMs back in manually and left it unpatched.  Seems like patching is not a good idea, even though it's critical.

0 Kudos
VMAKS
VMware Employee
VMware Employee

@amirzadeh

Thank you for the update.
Before patching VCSA please take a back of the vCenter and take a non-memory, non-quiesced snapshot of the vCenter VM(and PSC if it is external), before implementing any change.
Ensure that you have the login credential for the ESXi host which has the vCenter VM.

Then you can download the VCSA patch which should end with FP.iso from my.vmware.com > selecting VC and the version.
Upload the file to a datastore and map it to the VCSA VM through CD / DVD Drive option.
Patch the VCSA from CLI.

Run the following commands

software-packages stage –-iso

software-packages list –-staged

software-packages install –-staged

Reboot the VCSA VM.

This should patch the VCSA

 

Arun Kumar

Install / Upgrade

View solution in original post

0 Kudos