VMware Cloud Community
novell1
Enthusiast
Enthusiast
Jump to solution

VCSA Update from 7.0.3.00000 to 7.0.3.00300 failed

Hi, I did connect to the VCSA the VMware-vCenter-Server-Appliance-7.0.3.00300-19234570-patch-FP.iso . After the VCSA has startet in putty i start at the command >software-packages stage --iso --acceptEulas. I get :

[2022-02-02 18:11:18,943] : Discovering updates...
[2022-02-02 18:11:24,315] : UpdateInfo: Using product version 7.0.3.00000 and build 18700403
[2022-02-02 18:11:24,315] : Target VCSA version = 7.0.3.00300
[2022-02-02 18:11:54,599] : Stage path file doesn't exist
[2022-02-02 18:11:54,612] : Staging failed. Retry to resume from the current state. Or please collect the VC support bundle.
Command>

Do the VCSA not find the iSO File? I tried several other location on datastore, the same result....

What should I do?

Thanks for your help!

Werner

Reply
0 Kudos
1 Solution

Accepted Solutions
Anil0210
Enthusiast
Enthusiast
Jump to solution

Hello Werner,

Can you try following and let me know if it resolves.

- Log in to your vCenter Appliance via SSH.

- Run following command:

  software-packages unstage 
- Start the update process again. - software-packages stage --iso --acceptEula

View solution in original post

6 Replies
Anil0210
Enthusiast
Enthusiast
Jump to solution

Hello Werner,

Can you try following and let me know if it resolves.

- Log in to your vCenter Appliance via SSH.

- Run following command:

  software-packages unstage 
- Start the update process again. - software-packages stage --iso --acceptEula
novell1
Enthusiast
Enthusiast
Jump to solution

Hi Anil0210

In the vCenter Server Management VCSA GUI it does a pre check successfully, after that return to a new precheck, never ending loop.

After unstage, I could upgrade to 7.0.3! Thanks a lot!!!

You are really simpliy the best!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Thanks

Werner

Reply
0 Kudos
Anil0210
Enthusiast
Enthusiast
Jump to solution

Your Welcome Werner,

Glad to hear this worked for you. This is kind of known issue due to the patching DB having some stale entry from an earlier successful upgrade. Will look if any existing KB available for this.

 

~Anil

Reply
0 Kudos
MrContainer
Contributor
Contributor
Jump to solution

Spoiler
 We can't stage the update

We have the apparent same issue.

We get 

[2022-02-22 14:38:25,905] : Discovering updates...
[2022-02-22 14:39:35,363] : UpdateInfo: Using product version 7.0.3.00100 and build 18778458
[2022-02-22 14:39:35,363] : Target VCSA version = 7.0.3.00300
[2022-02-22 14:40:05,277] : Stage path file doesn't exist
[2022-02-22 14:40:05,285] : Staging failed. Retry to resume from the current state. Or please collect the VC support bundle.

We've tried from GUI and CLI

We have tried to stage and unstage and always get this same response.

We cant do the list -- staged  it just doesn't see anything.

Command> software-packages list --staged

[2022-02-23 08:31:35,541] : List packages failed
Command>

Any ideas? TIA

I'm not sure how it can ID what we have installed and what we want to go to BUT say the "Stage path file doesn't exist"

Reply
0 Kudos
EugeniusIT
Contributor
Contributor
Jump to solution

I was trying to go from 7.0.3.00600-19717403 (7.0U3E) to 7.0.3-20150588 (7.0U3g) and broke. We have 3x Dell R640 hosts running 7.0U2 (DEL-ESXi-702_17867351-A05). What is the fix for this or do we have to completely delete the vCenter VM and start over from scratch? Restore from backup not working "A problem occurred while logging in. Verify the connection details.".

Command> shell
Shell access is granted to root
root@vcenter-hostname [ ~ ]# rm /etc/applmgmt/appliance/software_update_state.conf
root@vcenter-hostname [ ~ ]# rm /storage/db/patching.db*
root@vcenter-hostname [ ~ ]# rm -rf /storage/core/software-update/updates
root@vcenter-hostname [ ~ ]# rm -rf /storage/updatemgr/software-*
root@vcenter-hostname [ ~ ]# rm -r /storage/core/software-update/*
root@vcenter-hostname [ ~ ]# appliancesh
Password:
Connected to service

* List APIs: "help api list"
* List Plugins: "help pi list"
* Launch BASH: "shell"

Command> software-packages stage --iso --acceptEulas

[2022-07-25 12:46:22,298] : Discovering updates...
[2022-07-25 12:46:24,223] : UpdateInfo: Using product version 7.0.3.00600 and build 19717403
[2022-07-25 12:46:24,224] : Target VCSA version = 7.0.3.00800
[2022-07-25 12:46:53,123] : Stage path file doesn't exist
[2022-07-25 12:46:53,126] : Staging failed. Retry to resume from the current state. Or please collect the VC support bundle.
Command> software-packages unstage

[2022-07-25 12:48:48,843] : Unstage operation completed successfully
Command> software-packages stage --iso --acceptEulas

[2022-07-25 12:48:53,815] : Discovering updates...
[2022-07-25 12:48:55,687] : UpdateInfo: Using product version 7.0.3.00600 and build 19717403
[2022-07-25 12:48:55,687] : Target VCSA version = 7.0.3.00800
[2022-07-25 12:49:24,615] : Stage path file doesn't exist
[2022-07-25 12:49:24,618] : Staging failed. Retry to resume from the current state. Or please collect the VC support bundle.
Command>

Reply
0 Kudos
EugeniusIT
Contributor
Contributor
Jump to solution

After working with VMWare tech support they were able to get things up and running (renew expired machine cert and start up services that were not running) but we were still running into the upgrade issue where the VCSA was showing the older version but inside the config files it was showing the latest. We had two options. Option 1 was to just wait for a new release then try but he didn't think it was going to work so we decided to do Option 2 which was to re-deployed from scratch and re-added the hosts. During the t-shooting there was a expired machine cert which could have possibly caused the issue. This can be reviewed in Administration > Certificate Management.

Reply
0 Kudos