I have just had the pleasure of running into this bug when replacing a ESXi host in our vsphere cluster.
There is no fix but a workaround. And thats all fine... except there is no description for a workaround if you are running VCSA...
Have anyone else had this problem with VCSA? and maybe now if there's a fix... workaround.. anything.
Thanks
/Tomas