Symptoms
YYYY-MM-DDTHH:MM:SS.000+0000 ERROR [vcf_dm,aaaaaaaaa] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-5] [TU1P8P] SSO_CANNOT_DECOMMISSION_NODE Node < vCenter FQDN > decommission could not be initiatedNote : If other errors such as “Fetched topology with 3 nodes, contains nodes with invalid partner count, invalid ones” are recorded in domainmanager.log, resolving this KB's resolution alone will not fix the issue unless those problems are addressed.
com.vmware.evo.sddc.common.core.error.InvalidStateException: Node < vCenter FQDN > decommission could not be initiated
<snip>
Caused by: org.springframework.web.client.HttpServerErrorException$InternalServerError: 500 Internal Server Error: "{"type":"com.vmware.vapi.std.errors.internal_server_error","value":{"error_type":"INTERNAL_SERVER_ERROR","messages":[{"args":["com.vmware.vapi.std.errors.not_allowed_in_current_state","decommission$task"],"default_message":"Invalid error com.vmware.vapi.std.errors.not_allowed_in_current_state reported from method decommission$task.","id":"vapi.method.status.errors.invalid"},{"args":[],"default_message":"Duplicate decommission call. Ignoring call, as decommission is already in progress.","id":"com.vmware.appliance.DuplicateCallCheck"}]}}"
VMware SDDC Manager 4.5
VMware SDDC Manager 5.1
VMware SDDC Manager 5.2
VMware vCenter Server 7.0
VMware vCenter Server 8.0
This is because leaving decommission_status.json behind causes the decommissioning task to be identified as duplicated.
The background for retry “Decommission vCenter Server” is that other issues have occurred, and since those issues have been resolved, it is assumed this task will be retry.
Please verify that existing the snapshot of the vCenter and SDDC Manager taken before fixing the other issues before implementing the following workaround.
rm -rf /var/log/vmware/decommission/*
service-control --restart applmgmt