What happened:
When creating pods with a cinder volume, they may occasionally get stuck in the 'ContainerCreating' state. Upon closer examination, the disk appears with a size of 0B. This issue likely arises because occasionally hypervisors don't send a new volume size to the kernel when a volume is in use.
However, if we force a rescan of the block device on the node by executing echo "1" > /sys/class/block/[device]/device/rescan, the pod will start
What you expected to happen:
The pod to be started normally
How to reproduce it:
Issue it not consistently reproducible
Would it be possible to add the rescan bit during provisioning if it fails, not only on resize? I understand there might be a slight challenge since not all devices support this. However, we can check if the paths exists or if rescan-on-resize is set, could we also set the rescan bit?
Similar to the probeVolume case where "- - -" is set to /scan, we would also set "1" to /rescan as the "- - -" won't cover the case were the size is incorrectly reported
What happened: When creating pods with a cinder volume, they may occasionally get stuck in the 'ContainerCreating' state. Upon closer examination, the disk appears with a size of 0B. This issue likely arises because occasionally hypervisors don't send a new volume size to the kernel when a volume is in use.
However, if we force a rescan of the block device on the node by executing echo "1" > /sys/class/block/[device]/device/rescan, the pod will start
What you expected to happen:
The pod to be started normally
How to reproduce it:
Issue it not consistently reproducible
Would it be possible to add the rescan bit during provisioning if it fails, not only on resize? I understand there might be a slight challenge since not all devices support this. However, we can check if the paths exists or if rescan-on-resize is set, could we also set the rescan bit?
Similar to the probeVolume case where "- - -" is set to /scan, we would also set "1" to /rescan as the "- - -" won't cover the case were the size is incorrectly reported
/kind bug