-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RBD: Snapshots >450 cannot be taken on a PVC in certain cases #4069
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation. |
Describe the bug
CephCSI follows the below logic before a k8s snapshot or pvc-pvc clone is created.
ceph-csi/internal/rbd/controllerserver.go
Lines 532 to 539 in a57fe08
But if the cloned image[1] is in trash[2],
CephCSI still tries to add a task to flatten that cloned image (without checking if it is in trash) and fails.
The failure is only logged. CephCSI will not be able to create any more snapshots or pvc-pvc clones once the number hits 450+.
[1] cloned image: underlying a k8s snapshot or pvc-pvc clone)
[2] image in trash: this occurs when the image has child images of its own still alive.
Environment details
fuse
orkernel
. for rbd itskrbd
orrbd-nbd
) : rbdSteps to reproduce
Steps to reproduce the behavior:
Actual results
The final snapshot creation fails.
Expected behavior
Snapshots should be created without error.
Propose solutions 1:
During k8s Snapshot Deletion :
@idryomov @Madhu-1 @nixpanic Can you please provide your opinions/suggestions regarding this?
The text was updated successfully, but these errors were encountered: