VCSA upgrade 7.0 to 7.0 U2 - cannot resume upgrade

[HCBV]

I tried upgrading vCenter SA 7.0.1.00300 to 7.0.2.000000 but it failed.

Tried method: update through VAMI, as I usually do. Made a back-up, search the online repo and tried updating. This failed.

I got stuck in a loop and ended up deleting the /etc/applmgmt/appliance/software_update_state.conf file to regain control and be able to login.

Retry resulted in the same error.

I then downloaded VMware-vCenter-Server-Appliance-7.0.2.00000-17694817-patch-FP and mounted the ISO on the vCenter machine and tried upgrading from within VAMI through the CD-rom repo. This now results in the following error:

"Resume attempted maximum number of times. Cannot resume patching anymore."

How should I solve this problem?

my esxi hosts are already updated to VMware ESXi, 7.0.2, 17630552

[Ajay1988 · Accepted solution]

reboot the VCSA once and after al services r back up . Try the patching via cli .

Attach the VMware-vCenter-Server-Appliance-7.0.2.00000-17694817-patch-FP.iso file to the vCenter Server CD or DVD drive.

Log in to the appliance shell as a user with super administrative privileges (for example, root) and run the following commands:
To stage the ISO:
software-packages stage --iso

To see the staged content:
software-packages list --staged

To install the staged rpms:
software-packages install --staged

[HCBV]

I initially had problems after restarting VCSA.

The content library containing the patch ISO was missing.

This was fixed by removing the .conf file that keeps VCSA in the update loop. Then I did the update method as described. This works. Perfect!

[jceron11]

Hi all

in my case I solved it by executing the following command from the console of the vcenter appliance

software-packages install --url

the process take about 10 minutes and finish without errors

Do you accept the terms and conditions? [yes/no] yes
[2021-04-07T22:36:37.097] : Evaluating packages to stage...
[2021-04-07T22:36:37.097] : Verifying staging area
[2021-04-07T22:36:37.097] : For the first instance of the identity domain, this is the password given to the Administrator account. Otherwise, this is the password of the Administrator account of the replication partner.
Enter Single Sign-On administrator password:

[2021-04-07T22:36:44.097] : Validating software update payload
[2021-04-07T22:36:44.097] : UpdateInfo: Using product version 7.0.1.00300 and build 17491101
[2021-04-07 22:36:44,715] : Running validate script.....
[2021-04-07T22:36:47.097] : Validation successful
[2021-04-07 22:36:47,726] : Copying software packages 152/152
[2021-04-07 22:41:38,369] : Running system-prepare script.....
[2021-04-07 22:41:42,383] : Running test transaction ....
[2021-04-07 22:41:44,399] : Running prepatch script.....
[2021-04-07 22:44:21,593] : Upgrading software packages ....
[2021-04-07T22:45:59.097] : Setting appliance version to 7.0.2.00000 build 17694817
[2021-04-07 22:45:59,752] : Running patch script.....
[2021-04-07 22:54:37,723] : Starting all services ....
[2021-04-07T22:54:38.097] : Services started.
[2021-04-07T22:54:38.097] : Installation process completed successfully

[HCBV]

I am now starting to experience serious issues with VCSA and ESXi hosts after the upgrade.

For the 3rd time a hosts VM's become uncontrollable.

I can still ping them, use remote control to gain access but I cant reboot or shutdown the guest os.

Even doing a reboot or kill via the esxi host command "vim-cmd vmsvc/power.off X" does nothing.

I can login to both the ESXi host and VCSA. But I can't control the VM's anymore.

This happens after about 2 days while running succesfully.

[bbeham4004]

look at both memory errors and/or storage becoming detached.  I know this has caused those same issues for me historically.  A remote session with vmware will get to the root of the problem.  Its usually hardware related.

[cedric_datawan]

Hi,

I've the same loop,

What is the .conf file you have suppres ?

Thanks

[Ajay1988]

Remove /etc/applmgmt/appliance/software_update_state.conf file and reboot the VCSA and do cli patching after taking snapshot