Possible leaks in cephcsi (question)

[Madhu-1]

Possible leaks in cephcsi (question)

General leak

CreateVolume/CreateSnapshot

• we create a new UUID entry in the omap and we add a mapping between the new UUID and PV Name and we go ahead and create the volume

What if the csi pod is restarted between the new UUID and PV mapping? will this leave a stale entry?

Note: We also need to check restart of csi-provisioner container will leave any stale PVC,PV,ceph resource in cluster?

RBD

Create Volume

• Reserve omap
  • Possible leak as mentioned in the general section?
• Create rbd image

Create volume from the snapshot

• Reserve omap and create a clone from the snapshot already created
• Only the omap leak can occur

Create Volume from volume

• Reserve omap
  • Possible leak as mentioned in the general problem?
• Create snapshot from rbd image
• Create temp clone from rbd image
  • what if there is a csi pod restart here, is this handled?
• Check flatten is required and add a task to flatten the image
  • • what if there is a csi pod restart here, is this handled?
• remove the snapshot from the rbd image
  • what if there is a csi pod restart here, is this handled?
  • what if the snapshot cannot be deleted?
• create a snapshot on temp clone image.
  • what if there is a csi pod restart here, is this handled?
• create a final clone from temp clone
  • what if there is a csi pod restart here, is this handled?
• Delete snapshot on the temp clone
  • what if there is a csi pod restart here, is this handled?
  • what if the snapshot cannot be deleted?

Create snapshot

• Reserve omap
  • Possible leak as mentioned in the general section?
• Create snapshot from rbd image
• Create a clone from the rbd image
  • what if there is a csi pod restart here, is this handled?
• remove the snapshot from the rbd image
  • what if there is a csi pod restart here, is this handled?
  • what if the snapshot removal fails?
• create a snapshot on clone image.
  • what if there is a csi pod restart here, is this handled?

Delete Volume

Note covered in #1728?

• Move the image to the trash
  • what if there is a csi pod restart here, is this handled?
• Add task to remove the image from trash
  • what if there is a csi pod restart here, is this handled?
• Cleanup omap

CephFS

Create Volume

• Reserve omap
  • Possible leak as mentioned in the general section?
• Create subvolume

Create volume from the snapshot

• Reserve omap
  • Possible leak as mentioned in the general section?
• create a clone from the snapshot already created

Create Volume from volume

• Reserve omap
  • Possible leak as mentioned in the general problem?
• Create snapshot from cephfs subvolume
• Create a clone from a snapshot
  • what if there is a restart here is this handled?
  • If the clone creation fails and also snapshot deletion fails will this leave a stale snapshot here?
• If the clone is ready remove the snapshot
  • what if there is a restart here is this handled?
  • what if the snapshot cannot be deleted?

Create snapshot

• Reserve omap
  • Possible leak as mentioned in the general problem?
• Create snapshot subvolume

[Madhu-1]

@nixpanic @ShyamsundarR @humblec @Yuggupta27 @Rakshith-R @yati1998 Do you guys any other possibilities we need to check?

[Madhu-1]

cc @agarwal-mudit

[Madhu-1]

There may/may not be a leak in above cases but we need to verify and make sure there is no leak

[humblec]

As discussed we have to continue the analysis and get into the completion in upcoming releases. Moving this out of 3.4.0 release.

[github-actions]

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.

[github-actions]

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

[humblec]

@Madhu-1 shall we remove this form the milestone tracker?