v1/releases/domains endpoint is invoked via custom automation using the following payload, the target version is applied directly to the vCenter, bypassing the SDDC Manager update process.{ "targetVersion": "5.2.1.0", "patches": [ { "productType": "SDDC_MANAGER", "version": " 5.2.2.0-24936865" }, { "productType": "VCENTER", "version": "' 8.0.3.00600-24853646" } ]}
/var/log/vmware/vcf/lcm/lcm-debug.log, the following will be seen.YYYY:MM:DDTHH:MM:SS DEBUG [vcf_lcm,6973054e661e3acdf1b8f9412b740641,7dcc] [c.v.v.l.r.a.c.v.u.DomainReleaseViewController,http-nio-127.0.0.1-7400-exec-8] Save target vcf version {"targetVersion":"5.2.1.0","patches":[{"productType":"VCENTER","version":"8.0.3.00600-24853646"}]} for domain 7XXXXXXX-5XXX-4XXX-aXXX-0XXXXXXXXXXXX
YYYY:MM:DDTHH:MM:SS DEBUG [vcf_lcm,697305a37597c98948747f7142f22aef,9f62] [c.v.v.l.r.a.c.v.u.DomainReleaseViewController,http-nio-127.0.0.1-7400-exec-2] Save target vcf version {"targetVersion":"5.2.1.0","patches":[{"productType":"SDDC_MANAGER","version":"5.2.2.0-24936865"},{"productType":"VCENTER","version":"8.0.3.00600-24853646"}]} for domain 7XXXXXXX-5XXX-4XXX-aXXX-0XXXXXXXXXXXX
The issue was identified to be logic miss on the custom Automation which passes only {"productType": "VCENTER","version": "' 8.0.3.00600-24853646"} in its first attempt, and then pasess the whole payload the second time.
To resolve the issue, invoke the API from the SDDC manager UI.
{ "targetVersion": "5.2.1.0", "patches": [ { "productType": "SDDC_MANAGER", "version": " 5.2.2.0-24936865" }, { "productType": "VCENTER", "version": "' 8.0.3.00600-24853646" } ]}
6. Click invoke.
7. Result 200 will be reported indicating a successful API invocation.
8. Navigate to Workloads- > Management domain -> Updates
9. The sddc manager update will now be available to be initiated.