Same issue here, I posted a few days ago here: On-Premise VSphere provisioning with Rancher 2.3.3 and 2.3.4. My workaround was to downgrade to 2.3.2, which still talks to my vcenter environment reliably.
Same issue here, I posted a few days ago here: On-Premise VSphere provisioning with Rancher 2.3.3 and 2.3.4. My workaround was to downgrade to 2.3.2, which still talks to my vcenter environment reliably.