Bug 1119236
| Summary: | Restart engine during live snapshot creation reported as failed by engine but created successfully | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Raz Tamir <ratamir> | ||||
| Component: | ovirt-engine-core | Assignee: | Allon Mureinik <amureini> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Aharon Canan <acanan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5 | CC: | acanan, acathrow, amureini, gklein, iheim, ratamir, s.kieske, yeylon | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | 3.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-07-14 12:07:48 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: |
|
||||||
Why is this considered "not a bug"? Doesn't this lead to an inconsistent state in ovirt-engine? Update: This bug is not depend on restarting engine. The relevant bug is: https://bugzilla.redhat.com/show_bug.cgi?id=1119203 |
Created attachment 917748 [details] vdsm and engine logs Description of problem: If restarting the engine during a live snapshot creation, the engine reports that "Failed to complete snapshot 'snapshot_343077' creation for VM 'vm_0'." but the snapshot created successfully and the volumes created too. Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch vdsm-4.16.0-3.git601f786.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start a live snapshot operation 2. restart engine service 3. Actual results: The snapshot is created and all the volumes exists and the failure message is shown. Expected results: the snapshot should succeeded with no Failure message OR the snapshot creation should fail with failure message Additional info: