Upgrade vMA 4.0 to 4.1 using vima-update

[q8_it]

In the release notes of vma 4.1 (http://www.vmware.com/support/developer/vima/vma41/vma_41_relnotes.html) it seems possible to update the appliance from 4.0 to 4.1 using vima-update:

Important: You can use the

vima-update

utility to
update VIMA 4.0 to vMA 4.1 GA. You cannot, however, use the

vima-update

utility to upgrade VIMA 1.0 to vMA 4.1.

I've tried with "sudo /usr/sbin/vima-update scan" but it found nothing, same for "sudo /usr/sbin/vima-update update", it return:

Skipping bulletin VIMA400-200911002, it is installed or obsoleted

Skipping bulletin VIMA400-200906001, it is installed or obsoleted

Skipping bulletin VIMA400-201002201, it is installed or obsoleted

Nothing to update.

I've searched on the documentation but did not found anything related to update/upgrade with vima-update..

Anyone know how to do it?

[lamw]

I would hold off in terms of upgrading, there's just too many little issues that people are reporting.

I would definitely do this in a dev environment to ensure that nothing is broken before pushing it out to a production vMA host. Unfortunately I just don't have the cycles to go through and validate all scripts. The ones I would be worried about is ghettoVCBg2 and UPS script, these are utilizing the vi-fastpass library and assuming nothing else has change, it should work.

Do let me know if you run into any issues and I can take a look at it when I get a chance.

Thanks

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

[KKrtz]

I still have the error after the update "The format of the metadata is invalid" when I redo the command "sudo vma-update scan"

Any news ?

[lamw]

The reason for this is the URL metadata is still not available, once VMware posts that then the error will go away. Since there are no post vMA 4.1 patches, you don't need to worry about this error. I still have not gotten word back that this will be fixed, so hopefully it'll be soon.

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

[OM4EVER]

William has this issue been resolved regarding the URL and metadata? I upgraded from the VIMA1.0 to the VMA but in doing the SCAN I still get the error message.

Thanks for all your help

[lamw]

Nope it still has not but it should not affect your system since there are no vMA 4.1 patches.

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

[cskowmh]

Oddly the error I'm getting suggests the .zip file for the metadata isn't a .zip file at all

[vi-admin@XXXXXXXX ~]$ sudo vma-update scan
Password: 
                                                              ####################################################################################### [100%]

Encountered error MetadataFormatError:
The error data is:
   Filename    - /var/tmp/esxupdate/metadata-2760350473111833260/metadata.zip
   Message     - Error unzipping
                 /var/tmp/esxupdate/metadata-2760350473111833260/metadata.zip:
                 File is not a zip file
   Errno       - 5
   Description - The format of the metadata is invalid.
[vi-admin@XXXXXXXX ~]$ file /var/tmp/esxupdate/metadata-2760350473111833260/metadata.zip
/var/tmp/esxupdate/metadata-2760350473111833260/metadata.zip: UTF-8 Unicode HTML document text, with very long lines, with CRLF, CR, LF line terminators
[vi-admin@XXXXXXX ~]$ head -2 /var/tmp/esxupdate/metadata-2760350473111833260/metadata.zip

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
[vi-admin@XXXXXXXX ~]$

[lamw]

Yes, the reason being is the zip file that is supposed to be hosted on VMware's site is not available. Hence, after the upgrade, if you decide to run "sudo vma-update scan", it'll fail. This is a known issue and I've already pinged the vMA PM but I have not heard back

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".