/var/log/vmware/vcf/lcm/tools/asyncpatchtool/async_patch_tool.log:
2025-01-09T09:48:24.888+0000 [main] ERROR [com.vmware.evo.sddc.lcm.tools.asyncpatch.AsyncPatchToolMain]
PARTNER_BUNDLE_INVALID
-- Error Message: Partner bundle metadata does not contain bundle with given version
-- Remedy: null
-- Error Stacktrace:
com.vmware.evo.sddc.lcm.model.error.LcmException: Partner bundle metadata does not contain bundle with given version
at com.vmware.evo.sddc.lcm.tools.asyncpatch.VxRailUtils.findAndCopyPBMForVxRailBundle(VxRailUtils.java:119)
at com.vmware.evo.sddc.lcm.tools.asyncpatch.VxRailUtils.replaceDepotPBMWithAsyncPatchPBM(VxRailUtils.java:54)
at com.vmware.evo.sddc.lcm.tools.asyncpatch.AsyncPatchToolHelper.constructBundleDownloadSpec(AsyncPatchToolHelper.java:365)
at com.vmware.evo.sddc.lcm.tools.asyncpatch.EnablePatchSpecHelper.constructInputSpec(EnablePatchSpecHelper.java:58)
Patch enablement fails.
VCF 4.5.x
As per https://knowledge.broadcom.com/external/article/324139/prerequisite-before-enabling-vxrail-asyn.html, in VxRail environments, it is essential that the relevant partnerBundleMetadata.json file is downloaded and moved to the correct location on the SDDC to allow VxRail patch enablement to succeed.
The failure described here can occur in three scenarios:
As per https://knowledge.broadcom.com/external/article/324139/prerequisite-before-enabling-vxrail-asyn.html:
"Copy the downloaded patch-specific partner bundle metadata file to the AP tool output directory where patch bundles will be downloaded. If you have not specified the --ouputDirectory, the default output directory will be {user.home}/apToolBundles"
It is also important that the downloaded file NOT be renamed.
For example, if you are trying to enabled the VxRail 7.0.531-28777448 patch, the required download bundle is partnerBundleMetadata_7_0_531_28777448.json.
Make sure when you move the file to the SDDC Manager you preserve the naming convention ( partnerBundleMetadata_7_0_531_28777448.json
).
Do not rename it to 'partnerBundleMetadata.json'