This is a known issue affecting VMware Cloud Foundation.
Currently, there is no resolution.
To work around this issue, update the NSX Manager version manually:
- Log in to the SDDC Manager virtual machine (VRM) as the root user through SSH or console.
- Run this command to determine the ID of the Workload Domain where the NSX Manager resides:
curl -i -X GET http://localhost:8080/vrm-ui/api/1.0/vrm/logical-inventory/domains/
Note: You see output similar to:
[{"type":"IaaS","domainId":"e455705b-8d8e-4889-b4d5-2facb26bf321","domainName":"Domain2"},{"type":"MANAGEMENT","domainId":"c6925a57-3210-306e-a416-98b82effdf24","domainName":"Management-gss-vrack1"},{"type":"IaaS","domainId":"ff3f197f-3864-4eda-8083-bffc2acb3ba4","domainName":"SG-Test"}]
Note: In this example, the Workload Domain is Domain2 and its ID is e455705b-8d8e-4889-b4d5-2facb26bf321.
- Edit the /tmp/payload.json file, using a text editor.
Example output:
{
"id": "e455705b-8d8e-4889-b4d5-2facb26bf321",
"type": "NSX_MANAGER",
"value": "6.2.4-4292526"
}
Note: Ensure that the id value is the one obtained in Step 2 and that the value is the correct version and build number for the NSX Manager in question.
- Run this command to update the NSX Manager version:
curl -i -w "\n" http://localhost:8080/vrm-ui/api/1.0/vrm/logical-inventory/action/entity/version -X POST -d @/tmp/payload.json --header "Content-Type: application/json"