KreVet-Ka opened a new issue, #13051:
URL: https://github.com/apache/cloudstack/issues/13051

   ### problem
   
   Bug report:
   CloudStack allows creating multiple snapshots of the same volume with 
identical names.
   
   <img width="1126" height="307" alt="Image" 
src="https://github.com/user-attachments/assets/789aad21-4259-4d36-aafd-91a21770027f";
 />
   These snapshots are treated as separate entities in CloudStack, but they 
reference the same snapshot file on secondary storage.
   
   <img width="1335" height="86" alt="Image" 
src="https://github.com/user-attachments/assets/a55a91f4-729e-496f-823c-b4c1a2e7d970";
 />
   
   The snapshot file on secondary storage is overwritten when a snapshot with 
the same name is created
   <img width="1430" height="281" alt="Image" 
src="https://github.com/user-attachments/assets/9dea9d6d-0a85-49ee-8b7d-d7de77d56717";
 />
   
   When one of these snapshots is deleted via CloudStack. The snapshot file is 
removed from secondary storage. Other snapshot entries remain in CloudStack but 
no longer have a corresponding file.
   
   Deleted a snapshot in Cloudstack
   <img width="1416" height="267" alt="Image" 
src="https://github.com/user-attachments/assets/be66b591-9af6-4b0b-9fcb-78d2ff021248";
 />
   The first snapshot was deleted from CloudStack. During the deletion process, 
CloudStack also removed the snapshot file from secondary storage.
   
   <img width="1609" height="390" alt="Image" 
src="https://github.com/user-attachments/assets/e981baeb-6877-4b0d-a2dd-7869a3258657";
 />
   
   However, a second snapshot entry still remains in the database and 
references a file on secondary storage that no longer exists.
   
   <img width="1481" height="106" alt="Image" 
src="https://github.com/user-attachments/assets/27b70acf-2789-46e1-b1ae-bdc35f2fe1b7";
 />
   
   ### versions
   
   ACS: 4.20.2.0
   Hypervisor: KVM
   Primary Storage: Linstor
   Secondary Storage: NFS
   
   
   ### The steps to reproduce the bug
   
   1. Create a volume
   2. Create snapshot with name "test-snapshot"
   3. Create another snapshot with the same name "test-snapshot"
   4. Verify that both snapshots exist in CloudStack
   5. Delete ONE of the snapshots via CloudStack
   6. Check secondary storage — snapshot file is removed
   7. Check remaining snapshot in CloudStack
   
   ### What to do about it?
   
   Prevent creating snapshots with the same name for the same volume. Deleting 
one breaks the other.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to