When cluster is installed via assisted-installer we start with fake credentials and untaint node to pretend they are initialized (see related https://issues.redhat.com/browse/MGMT-13605).

Afterwards console plugin is used to provide real credentials. On 4.12.0 this method works and all operators are healthy. On latest 4.13 nightly storage operator complains that it can't find VM via UUID

latest 4.13 nightly

Always

1. Install latest 4.13 nightly using assisted installer
2. Provide valid vSphere credentials
3. Create a PVC

"VSphereProblemDetectorControllerAvailable:      unable to find VM by UUID" error in storage operator conditions.

PVCs stuck in Pending

All operators are healthy, PVCs can be provisioned

Workaround:
* re-add node.cloudprovider.kubernetes.io/uninitialized taint on all nodes
* update credentials via the plugin
* restart vSphere cloud controller pods