I was able to avoid this issue in a similar way:
I added the host to another vcenter instance. This successfully unassociated it with the current vcenter.
I then added it back.
I was able to avoid this issue in a similar way:
I added the host to another vcenter instance. This successfully unassociated it with the current vcenter.
I then added it back.