Unrecognized file vendor-index.xml in Metadata file

[RobHay81]

When I try to scan an ESXi 5 host I get the error "Host cannot download files from VMware vSphere Update Manager patch store.  Check network connectivity and firewall setup, and check esxupdate"

On checking the log I can see the following error "Unrecognized file vendor-index.xml in Metadata file" as per below:

2012-02-20T09:39:01Z esxupdate: downloader: DEBUG: Downloading http://10.50.18.10:9084/vum/repository/hostupdate/csco/csco-VEM-5.0.0-metadata.zip to /tmp/tmpog4fGM...

2012-02-20T09:39:01Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2012-02-20T09:39:01Z esxupdate: downloader: DEBUG: Downloading http://10.50.18.10:9084/vum/repository/hostupdate/csco/metadata_1320764850.zip to /tmp/tmpHTeDDs...

2012-02-20T09:39:01Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2012-02-20T09:39:01Z esxupdate: downloader: DEBUG: Downloading http://10.50.18.10:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.0.0-metadata.zip to /tmp/tmpmdTojg...

2012-02-20T09:39:01Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2012-02-20T09:39:01Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

Anyone able to help?  Have been on the phone with vmware support for 2.5 hours and still no resolution!

Thanks,

[RobHay81]

Cause

---------

This appears to be a differential in the way the Cisco patch creates a folder name for the Cisco repository, versus how Update Manager normally does it. The VUM created folder is in lower case (csco), but the metadata from this patch is looking for an upper case folder. Since Windows is fine to use either, the patch uploads successfully. However when the Tomcat server goes to pull down the patch to the host, the case sensitivity discrepancy breaks the download. This causes any Update Manager host Scans to fail.

Resolution

---------------

Resolution #1:

1.Open SQL Management Studio to the Update Manager Database 2. Expand Tables 3. Right-click the dbo.VCI_METADATA_FILES select 'Edit Top 200 Rows'

4. Find the entry for the new metatadate CISCO-VEM500-4.2.1.1.5.0-3.0.1-metadata_########.zip under e the RELATIVE_PATH column of this entry change the CSCO\ to csco\ 5. Restart the VUM service 6. Scanning and remediation should now work correctly.

Resolution #2:

1.Stop VMware vSphere Update Manager Service 2. Navigate to the vUM patch repository folder (C:\ProgramData\VMware\VMware Update Manager\ is the default in Windows 2008) and rename the "Data" folder to "Data.backup"

3. Remove vSphere Update Manager from Programs and Features in Windows 4. Reinstall vSphere Update Manager from the vCenter Server installation media and during the installation, when it prompts "Automatically Download Patch Metadata", uncheck this box. note: This is important so that Update Manager does not create the folder for the default VEM patch repository.

5. Once Update Manager is reinstalled, open a new vSphere Client and navigate to the Update Manager tab and click on Admin View.

6. Under the Configuration tab, click on Download Settings 7. Find the Cisco patch repository in the listing and uncheck the box 8. Click Apply and then Download Now. This will download the patch repository but will not create the folder with the "invalid" name.

9. Now you can once again create the baseline with the VEM500-201201140102-BG-release patch which will not cause a break this time.