Simultaneous concurrent snapshots for detached volume results in one of the snapshots in ALLOCATED state forever
Problem
Simultaneous concurrent snapshots for detached volume results in one of the snapshots in ALLOCATED state forever.
Steps to Reproduce the problem
- Create simultaneous snapshoMs on a detached volume either manually or by scheduling the snapshots.
- Verify the snapshots state, one of them would always fails to create and the state would remain as 'ALLOCATED' forever.
Root Cause
CloudPlatform doesn't support simultaneous concurrent snapshots on a detached volume, however when the snapshot creation fails the state is not updated as 'DESTROY' , rather it stays as 'ALLOCATED'.
Note: ESXi and KVM doesn't support concurrent snapshots however XenServer supports,this feature has been added in CloudPlatform 4.7.1 .
Required Modification
CloudPlatform code is fixed to change the snapshot state to 'DESTROY' when it fails to create when there are simultaneous concurrent snapshots on the same volume.
Reason for Modification
CloudPlatform shouldn't leave the failed snapshot in 'ALLOCATED' state.
Resolution/Workaround
CloudPlatform code is fixed to change the snapshot state to 'DESTROY' when it fails to create when there are simultaneous concurrent snapshots on the same volume.
Verification
1.Create simultaneous snapshots on a detached volume either manually or by scheduling the snapshots.
- Verify if failed snapshot state is changed to 'DESTROY'.
Impact on Existing System
This fix will make sure that the snapshots which fails to create doesn't leave a stale entry in 'ALLOCATED' state.
Potential Adverse Effect
There is no known adverse effect to the system
Document ID:
115000313526
Product:
CloudPlatform
Version:
4.3.0.2,4.5.0.0,4.5.1.0,4.7,4.7.1
Reference Jira ID:
CS-50190
Comments