Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Unable to upgrade host using esxupdate or import an ESX 4.1 upgrade bundle into Update Manager 4.1 (1024805)
Symptoms
- You are unable to import/upload the bundle upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip into VMware Update Manager 4.1
- You see the error:
[2010-07-28 13:38:35:607 'HostUpdateDepotManager' 3652 ERROR] [metadataCache, 98] Metadata file contains invalid content: Error: Platforms changed for bulletin: ESX410-GA-esxupdate
[2010-07-28 13:38:35:626 'ConfirmOfflinePatchTask.ConfirmOfflinePatchTask{12}' 3652 ERROR] [confirmOfflinePatchTask, 203] confirm Offline Patch failed with exception Error: Platforms changed for bulletin: ESX410-GA-esxupdate
[2010-07-28 13:38:35:632 'ConfirmOfflinePatchTask.ConfirmOfflinePatchTask{12}' 3652 INFO] [vciTaskBase, 1278] SerializeToVimFault fault:
(integrity.fault.FileUploadInvalidPackage) {
-
Upgrading an ESX 4.0.x host to ESX 4.1 via the esxupdate command as described in the vSphere Upgrade Guide may return the error:
[root@host]# esxupdate update --bundle=upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip
Encountered error MetadataFormatError:
The error data is:
Filename - None
Message - Duplicate definitions of bulletin ESX410-GA-esxupdate with
unequal attributes.
Errno - 5
Description - The format of the metadata is invalid. -
You see the error:
Failed to import data. Unable to persist upgrade package. Check if the package is already imported
Resolution
Note: If you have downloaded the Pre-Upgrade bundle after August 13, 2010, you should not encounter this issue. As of this date, the Pre-Upgrade package has been rebundled to prevent this issue.
Update Manager
This issue can be caused by using the pre-upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip bundle and uploading/importing itinto VMware Update Manager 4.1. The improper application of the pre-upgrade bundle causes a conflict between the ESX410-GA-esxupdate bulletin in the pre-upgrade bundle and a similar bulletin in the upgrade bundle.
To avoid encountering this issue, do not import/upload the pre-upgrade bundle into VMware Update Manager 4.1. VMware Update Manager 4.1 does not require this bundle for upgrade operations.
If you are currently experiencing this issue, contact VMware Technical Support for assistance. Reference this article in your Support Request. For more information, see How to Submit a Support Request.
Esxupdate
The issue in esxupdate can be caused by applying the pre-upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip twice prior to installing the upgrade bundle. The improper application of the pre-upgrade bundle causes a conflict between the ESX410-GA-esxupdate bulletin in the pre-upgrade bundle and a similar bulletin in the upgrade bundle.
To avoid encountering this issue, when using esxupdate, ensure to only apply the pre-upgrade package once prior to the upgrade bundle.
Alternatively, do not apply the pre-upgrade package at all. Instead, apply the esxupdate bulletin that is included in the upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip bundle.
Here's an example of the steps on how to do that:
-
Run # esxupdate --bundle <upgrade.zip> -b ESX410-GA-esxupdate update
-
Run # esxupdate --bundle <upgrade.zip> update
If you are currently experiencing this issue, remove or rename the /etc/vmware/esxupdate/bulletins.zip file, on the ESX host:
-
Run cd /etc/vmware/esxupdate.
-
Run mv bulletins.zip bulletins.old.
-
Apply the upgrade bundle by running:
esxupdate --bundle <upgrade.zip> update
Tags
Update-manager-host-upgrade-fails update-manager-import-offline-bundle-fails update-manager-download-patch-fails
Update History
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

