VMware Cloud Foundation during VCF LCM upgrade prechecks run, vCenter upgrade prechecks are failing at "VCENTER_BUNDLE_PRECHECK".

Products

• VMware Cloud Foundation

Issue/Introduction

The [stage bundle] step is failing during Bundle precheck of LCM vCenter upgrade prechecks run, as vCenter [stage bundle] API responds with error.

Symptoms:

• The below is the response received by LCM from vCenter during VCENTER BUNDLE PRECHECK during vCenter upgrade prechecks run.
• Error messages in LCM logs:

<VC FQDN> - NotFound (com.vmware.vapi.std.errors.not_found) => {
messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
id = com.vmware.appliance.update.not_found,
defaultMessage = Update 7.0.1.00200 is not found,
args = [7.0.1.00200],
params = ,
localized =
}],
data = ,
errorType = NOT_FOUND
}
 

Environment

VMware Cloud Foundation 4.2

Cause

vCenter returning the error response for staging bundle API: Update 7.0.1.00200 is not found.

Resolution

• Issue is resolved in VCF 4.3. For more information see VMware Cloud Foundation 4.3 Release Notes .
• For vCenter upgrades, all the API calls are moved to vAPI based calls, so this path will not be run and this issue will not occur.

Workaround:
To workaround this issue, please follow the below steps:

1. Login to vCenter appliance.
2. Stage the bundle through vCenter appliance. Please go to "Updates" -> "STAGE ONLY"
3. Re-run the bundle precheck on VCF LCM.

Additional Information

Impact/Risks:

• Issue is resolved in VCF 4.3.
• For vCenter upgrades, all the API calls are moved to vAPI based calls, so this path will not be run and this issue will not occur.