Bug 1050901
| Summary: | Failed to delete snapshot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Nicolas Ecarnot <nicolas> | ||||
| Component: | vdsm | Assignee: | Maor <mlipchuk> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Aharon Canan <acanan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.3 | CC: | acathrow, amureini, bazulay, bugs, iheim, mgoldboi, nicolas, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.4.1 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | ovirt-3.4.1-1.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-05-23 18:37:41 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Nicolas Ecarnot
2014-01-09 10:21:39 UTC
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. What's next is more or less related to the bug, as it deals with the now faulty VM, but is deals more with trying to run it, than to debug why the snapshot deletion failed. Anyway. Last news : - I saw that I was able to lvchange -aey (to activate) the logical volume, and then manually mount it (qemu-kvm). So it showed the information stored inside this volume was not corrupted. Weird or not, I was able to clone the whole VM definition AND the disk (using the web gui), not forgetting to rename each part (VM name, disk name). And the clone ran well! For the production part of my job, things are solved. But for the oVirt project, they're not. Good news : I still have the faulty VM available for your tests and tries. Semi-good news : I have another VM with a still running snapshot. You will understand I'm not fond of playing with the latter until we found a secure way to delete snapshots. On another way, I tried to compare the XML shown in the vdsm logs between the faulty VM and a VM running fine. Apart the many obvious differences (UID, paths), I see nothing shocking. This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1. Hi Nicolas, can u please also add sanlock and messages logs (also engine log could be great) I suspect it could be the same scenario as https://bugzilla.redhat.com/1082655 Hi, As I said on january, the concerned VM are production servers, so it is not straighforward for me to play with them. Some steps are to be taken before playing again with them, so please be patient and stay tuned. Thank you. Returning the needinfo flag to mark that we need more info to solve this issue. Nicolas, another question: does this failure reproduce consistently on ANY VM, or just on this specific one? Allon, Hard to say as we had only two VMs with snapshots. The first one was concerned, and the second one is running in production, and not payable with at present. This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.4.2 as it has severity high, please retarget if needed. If this is a blocker please add it to the tracker Bug #1095370 On my two oVirt setups, I upgraded to 3.4.1-1.el6. I just tested today and tried to reproduce the bug, and it does not appear anymore. I propose we close this bug. (In reply to Nicolas Ecarnot from comment #11) > On my two oVirt setups, I upgraded to 3.4.1-1.el6. > > I just tested today and tried to reproduce the bug, and it does not appear > anymore. > > I propose we close this bug. Thanks for the update, Nicolas! Closing. |