You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vSphere CSI Driver does not create FCD with CBT enabled, but when a customer uses some backup tooling somehow node VM got CBT enabled with all volumes attached to it. when this volume get detached from the Node and attempted to be attached to another node with CBT disabled, attach volume is failing with CnsFault error: CNS: Failed to attach disk when calling AttachDisk:Fault cause: vim.fault.InvalidState
Describe the solution you'd like
API should help clear enableChangedBlockTracking from FCD
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thanks for filing this. In this case all our customer saw was - CnsFault error: VSLM task failed . While we fix the flag on FCD, can we improve error reporting at least ?
Is your feature request related to a problem? Please describe.
When Node VM has no CBT but FCD has, FCD can not be attached to the Node VM.
Refer to the KB Article here - https://kb.vmware.com/s/article/88193 and GitHub Issue here - kubernetes-sigs/vsphere-csi-driver#1416 (comment)
vSphere CSI Driver does not create FCD with CBT enabled, but when a customer uses some backup tooling somehow node VM got CBT enabled with all volumes attached to it. when this volume get detached from the Node and attempted to be attached to another node with CBT disabled, attach volume is failing with
CnsFault error: CNS: Failed to attach disk when calling AttachDisk:Fault cause: vim.fault.InvalidState
Describe the solution you'd like
API should help clear enableChangedBlockTracking from FCD
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: