Upgrade VCSA 6.0.0b to 6.0 U1 or U1b fails

[SavkoorSuhas]

Hello,

So I am trying to upgrade my VCSA 6.0.0b to U1 or U1b and both of these fail.

Steps that I am doing:

1. Downloaded the ISO

2. Attached ISO to the appliance

3. SSH to the embedded PSC appliance vCenter.

4. Run the command:

software-packages install --iso --acceptEulas

software-packages install --iso --acceptEulas

[2016-02-11T23:21:12.042] : Staging software update packages from ISO

[2016-02-11T23:21:12.042] : ISO unmounted successfully

[2016-02-11T23:21:12.042] : CD drives do not have valid patch iso.

[2016-02-11T23:21:12.042] : Installation process failed

The error it fails with

So I downloaded the patch ISO for the appliance 6.0 from the KB

VMware KB: Full Patch for VMware vCenter Server 6.0

1. Attached this ISO to appliance

2. Run the same command and it stages successfully, but the install fails with the error:

running test transaction

installation process failed

No access to VAMI page as this is a GA?
Any thoughts?

On a side note, I was thinking, can I do the following?

1. Mount the 6.0 U1b ISO on a windows machine

2. Open vcsa.html

3. Click Upgrade and provide the details of the existing appliance.

Will this work?

Suhas

[vmEck]

What was the original error message (looks like it got cut out of your post or didn't paste properly).

Are you running an embedded PSC? If not, did you upgrade your PSC first?

Its a long shot, but did you do a CRC check on your ISO to make sure it matches? Or try to use the URL patching method instead of the ISO?

[SavkoorSuhas · Accepted solution]

I used the Patch ISO for 6.0 U1b, and the upgrade was successful.

It is quite funny, the upgrade for the same ISO failed on a Friday, but worked on a Monday. :smileygrin:

Suhas

[Devil_WAH]

Hi, I can tell you why it might have not worked one day but did the next. the storage log might be full, and this is only clean up on a schedual where old logs are compressed to Tar. so it might be the first attempts it was completly full, then the archiving of logs ran so the next time there was just enough free space for the update logs to get written.

<host>:/storage/log/vmware # df -h

Filesystem Size  Used Avail Use% Mounted on

..

..

/dev/mapper/core_vg-core 50G  2.3G   45G   5% /storage/core

/dev/mapper/log_vg-log 9.9G  9.6G     0 100% /storage/log

/dev/mapper/db_vg-db 9.9G  1.5G  8.0G  16% /storage/db

..

..

I then followed. https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21435...

<host>:/storage/log/vmware/sso # df -h

Filesystem Size  Used Avail Use% Mounted on

..

..

/dev/mapper/core_vg-core 50G  2.3G   45G   5% /storage/core

/dev/mapper/log_vg-log 9.9G  7.7G  1.7G  82% /storage/log

/dev/mapper/db_vg-db 9.9G  1.5G  8.0G  16% /storage/db

..

..

And the upgrade runs fine now.

So people having issue running upgrade I suggest having a look at the file space issues. Why VMware can't report its a space issue and not having us go hunting for the solution i don't know.

[ajkbond]

you need to download the patch not the build iso, download the patch from here, then your upgrade will work fine.

https://my.vmware.com/group/vmware/patch#search

for those who want to upgrade From U1 to U2B patch link below

VMware Knowledge Base