Hemant Kumar

I have been able to reproduce this issue. I am not sure if this is because of number of attached volumes on a node. I have vcenter logs and support...

We were able to reproduce this bug in a cluster on a node which has 30 volumes attached to it. The CSI driver supports 59 volumes to a node, so...

@divyenpatel I have not seen any detach failures in the KCM. We will try and reproduce it and see what is going on. If it is really a detach failure...

We ran the migration with 3.0.0-rc1, we haven't again tested with 3.0 final version but we managed to reproduce with 3.0.0-rc1. Unfortunately, I haven't had any luck after that one...

Yeah same for us. Migration is enabled automatically on upgrade and process is usually same for all cloudproviders. It is not feasible to add hooks for one cloudprovider to wait...

@divyenpatel does this require any changes in CSI driver or it is automatic? Also does 8.0u1 has fixes for both the issue we discussed above? 1. failed to set control...

More specifically, what we have noticed is - in 3.1.1, volume provisioning does not work if hosts are tagged. It only works if either computer clusters or datacenters are tagged....

Here is the backtrace when it failed. We are not using standalone hosts, but hosts are still part of the compute cluster. It is just that, host themselves are tagged:...

This is done - https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/testsuites/volume_expand.go