Bug 1635189
| Summary: | [downstream clone - 4.2.7] Engine marks the snapshot status as OK before the actual snapshot operation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | ovirt-engine | Assignee: | Benny Zlotnik <bzlotnik> |
| Status: | CLOSED ERRATA | QA Contact: | Yosi Ben Shimon <ybenshim> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.2.5 | CC: | ahadas, apinnick, audgiri, bscalio, bzlotnik, ebenahar, gveitmic, gwatson, jcrumple, michael.moir, mkalinin, peli, peter, ratamir, Rhev-m-bugs, sbonazzo, shipatil, tnisan |
| Target Milestone: | ovirt-4.2.7 | Keywords: | ZStream |
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.7.4 | Doc Type: | If docs needed, set a value |
| Doc Text: |
In the current release, the snapshot's status is locked until snapshot creation is complete.
|
Story Points: | --- |
| Clone Of: | 1628909 | Environment: | |
| Last Closed: | 2018-11-05 15:02:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1628909 | ||
| Bug Blocks: | |||
|
Description
RHV bug bot
2018-10-02 09:58:13 UTC
Eyal please have a look. Arik, do you have any insights from Virt side? (Originally by Tal Nisan) (In reply to Tal Nisan from comment #1) > Eyal please have a look. > Arik, do you have any insights from Virt side? That looks like a regression caused by the relatively recent changes in the create-snapshot command. The snapshot should indeed remain locked until all tasks are finished. (Originally by Arik Hadas) Benny, Can you please take a look? (Originally by Eyal Shenitzky) (In reply to Arik from comment #3) > (In reply to Tal Nisan from comment #1) > > Eyal please have a look. > > Arik, do you have any insights from Virt side? > > That looks like a regression caused by the relatively recent changes in the > create-snapshot command. The snapshot should indeed remain locked until all > tasks are finished. Actually, I was wrong, it seems that we unlocked the snapshot before calling the live-snapshot verb also in 4.1 [1], before those changes. [1] https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.1/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/snapshots/CreateAllSnapshotsFromVmCommand.java#L401-L404 (Originally by Arik Hadas) So, is it a Virt issue or Storage? (Originally by Tal Nisan) (In reply to Tal Nisan from comment #6) > So, is it a Virt issue or Storage? It can go either way but I would keep it as Storage since the storage team is the last to introduce a major change to the way this command operates. (Originally by Arik Hadas) *** Bug 1620087 has been marked as a duplicate of this bug. *** (Originally by Tal Nisan) Tested using: ovirt-engine-4.2.7.1-0.1.el7ev.noarch The snapshot's status stays locked till the snapshot creation completed. Moving to VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3480 sync2jira sync2jira |