An upgrade of the environment from VCF 9.0.0 to 9.0.1 is underway.
During the upgrade, all components in the management domain have been upgraded.
For the workload domain upgrade - the NSX upgrade from 9.0.0 to 9.0.1 shows as failed on the respective VCF Operations - Lifecycle - VCF Instances page -
Update failed at MMM DD, YYY, hh:mm:ss - Elapsed Time : X format-time-tick hours XX format-time-tick-minute XX format-time-tick-seconds
However, NSX has in fact successfully upgraded from 9.0.0 to 9.0.1 - as confirmed by reviewing the NSX Manager UI.
The SDDC Manager log /var/log/vmware/vcf/lcm/lcm-debug.log contains these entries -
Exception occurred during NSX API invocationjava.util.concurrent.ExecutionException: com.vmware.vapi.std.errors.InternalServerError: InternalServerError (com.vmware.vapi.std.errors.internal_server_error) (statusCode:500) => { messages = [], data = => {error_message=upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: 111, error_code=98, module_name=common-service}, errorType = INTERNAL_SERVER_ERROR
Initiating NSX UC Rollback with current attempt 1/2
Exception occurred during NSX API invocation java.util.concurrent.ExecutionException: com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) (statusCode:400) => { messages = [], data = => {error_message=Upgrade Coordinator rollback is temporarily disabled while the system upgrades the Upgrade Coordinator itself. Please try again later., httpStatus=BAD_REQUEST, error_code=31515, module_name=upgrade-coordinator}, errorType = INVALID_REQUEST
VCF 9.0.1
Intermittent issue related to a timing conflict.
Please open a case with Broadcom Support for assistance.