When two workload domains share an NSX instance (Shared NSX), after upgrading WLD1 using the custom patch, the Plan Upgrade / Change Summary for WLD2:
- Shows the wrong target for NSX
- Does not offer current NSX version in the dropdown
VCF 5.2.1
Part of the UI implementation considering shared NSX is missing.
This will be fixed in a future version.
As a workaround, the following steps using the API are available.
1. Click Inventory -> the target WLD, and verify that the recorded ID is included in the URL.
Example: https://[SDDC FQDN]/ui/sddc-manager/inventory/domains/mgmt-vi-domains/[ID]/summary
2. Open Developer Center -> API explorer.
3. Enter "v1/releases/domains/" in the filter and search.
4. Open Flexible Product Patches -> GET /v1/releases/domains/{domainId}/custom-patches
5. Enter the ID verified in step 1 into the domainId field, and check the applicable custom patch versions.
6. Open TargetUpgradeVersion -> POST /v1/releases/domains/{domainId}/validations.
7. Enter the ID recorded in step 1 into the domainId field, input the DomainRelease JSON containing the custom patch you wish to apply into the body, and execute.
Example(Using a custom patch for vCenter Server):
{
"targetVersion": "",
"targetVxRailVersion": "",
"patches": [
{
"productType": "VCENTER",
"version": "[vCenter Server version]"
}
]
}
8. Open GET /v1/releases/domains/validations/{validationId}, enter the validationId, execute it, and confirm from the results that there are no issues with the application.
9. Open PATCH /v1/releases/domains/{domainId}, enter the ID recorded in step 1 into the domainId field, enter the DomainReleaseView JSON information into the body, and execute.
Example(When using VXRail):
{
"targetVersion": "[targetVersion]",
"targetVxRailVersion": "[VxRailVersion]",
"patches": [
{
"productType": "VCENTER",
"version": "[vCenter Server version]"
}
]
}
10. Confirm that the Upgrade Sequence for vCenter Server and ESXi(or VxRail) is
displayed in the Available Updates of the target WLD.