Failed configuration updates, fetching subtask info errors related to SAML2 authentication, and depot settings status call failures have been observed during upgrades of the SDDC (Software Defined Data Center) Manager. These issues are accompanied by HTTP parsing issues for vCenter, LCM errors with missing bundle IDs, and incorrect database entries in the lcm/upgrade table.
VCF Upgrade Bundle not available or present to initiate and you may observe the following error in the GUI:
Retrieving update patches bundles failed. Unable to retrieve aggregated LCM bundles: Encountered error requesting http://127.0.0.1/v1/upgrades api - Encountered error requesting http://127.0.0.1/v1/upgrades api: A problem has occurred on the server. Please retry or contact the service provider and provide the reference token
VCF VMware SDDC Manager 5.x
An incomplete or improperly executed upgrade process leads to corrupted database entries within the Lifecycle Configuration Manager (LCM) and SDDC Manager databases. Specifically, upgrade tasks may be marked as "failed" instead of "completed with failure," preventing the system from correctly identifying failed upgrades and resulting in repeated errors during subsequent upgrade procedures.
Please contact Broadcom support for the resolution for this issue.
Error messages observed include "retrieving configuration updates failed" and "Fetching Subtask Info Error."
Depot settings status calls fail due to HTTP parsing issues for vCenter.
Debug logs indicate LCM errors related to missing bundle IDs and incorrect database entries.
The issue is also characterized by internal server errors (vcr_error_internal_server_error) when attempting upgrades.