Created attachment 944300[details]
log of failed BROKEN snapshot removal ...
Description of problem:
After overload on SPM node during snapshot deletion few snapshots remained in status BROKEN.
Now we can't delete/remove them.
SPM node load skyrocket when we marked 3 snapshot for deletion.
Version-Release number of selected component (if applicable):
RHEV: 3.4.2
How reproducible:
Every time
Steps to Reproduce:
1. Mark some big snapshot for deletion.
2. Load on SPM node rising to 30+, node unresponsive
3. SPM niode marked as unresponsible in RHEVM
4. SPM node rebooted
5. Snapshot marked as BROKEN.
6. Marking snapshot for deletion returns error:
Image does not exist in domain: 'image=206e6d62-7973-44d9-a245-59e3f88bde4a, domain=48f2b3b3-646d-4af5-91c0-ab50c8ff8e6d'
Actual results:
Snapshot remains in BROKEN status with above Error.
Expected results:
Snamshot deleted
Additional info:
attached log of snapshot deletion after snapshot is already in BROKEN state.
BROKEN snapshot is already removed in 3.5 as part of bug 1056935.
This change is more of a feature than a bug, and backporting it will neither be easy nor risk free. Unfortunately, there isn't a good way to provide this before 3.5 (which is already available as a beta version).
*** This bug has been marked as a duplicate of bug 1056935 ***
Created attachment 944300 [details] log of failed BROKEN snapshot removal ... Description of problem: After overload on SPM node during snapshot deletion few snapshots remained in status BROKEN. Now we can't delete/remove them. SPM node load skyrocket when we marked 3 snapshot for deletion. Version-Release number of selected component (if applicable): RHEV: 3.4.2 How reproducible: Every time Steps to Reproduce: 1. Mark some big snapshot for deletion. 2. Load on SPM node rising to 30+, node unresponsive 3. SPM niode marked as unresponsible in RHEVM 4. SPM node rebooted 5. Snapshot marked as BROKEN. 6. Marking snapshot for deletion returns error: Image does not exist in domain: 'image=206e6d62-7973-44d9-a245-59e3f88bde4a, domain=48f2b3b3-646d-4af5-91c0-ab50c8ff8e6d' Actual results: Snapshot remains in BROKEN status with above Error. Expected results: Snamshot deleted Additional info: attached log of snapshot deletion after snapshot is already in BROKEN state.