Bug 1628909
| Summary: | Engine marks the snapshot status as OK before the actual snapshot operation | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | nijin ashok <nashok> | |
| Component: | ovirt-engine | Assignee: | Benny Zlotnik <bzlotnik> | |
| Status: | CLOSED ERRATA | QA Contact: | Yosi Ben Shimon <ybenshim> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 4.2.5 | CC: | ahadas, audgiri, bscalio, bzlotnik, ebenahar, gveitmic, gwatson, michael.moir, mkalinin, mtessun, peli, peter, Rhev-m-bugs, shipatil, tnisan | |
| Target Milestone: | ovirt-4.3.0 | Keywords: | ZStream | |
| Target Release: | 4.3.0 | Flags: | lsvaty:
testing_plan_complete-
|
|
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-engine-4.3.0_alpha | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1635189 (view as bug list) | Environment: | ||
| Last Closed: | 2019-05-08 12:38:22 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1635189 | |||
|
Description
nijin ashok
2018-09-14 10:37:36 UTC
Eyal please have a look. Arik, do you have any insights from Virt side? (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. Benny, Can you please take a look? (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 So, is it a Virt issue or Storage? (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. *** Bug 1620087 has been marked as a duplicate of this bug. *** WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops
Tested using: ovirt-engine-4.3.0-0.6.alpha2.el7.noarch vdsm-4.30.4-1.el7ev.x86_64 - Tested both with and without 30 seconds delay in VDSM. - Tested with both VM states - up and down. - There were 5 preallocated disks of size 20G each. The snapshot creation process took much more than 10 seconds (~60 seconds). The whole operation time (till it completed), the snapshot status was locked (using REST API). Moving to VERIFIED WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops
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/RHEA-2019:1085 sync2jira sync2jira |