Bug 1488542
Summary: | "No such drive" error on live merge of one disk causes merge of other disk to fail on engine. | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Koutuk Shukla <kshukla> | |
Component: | vdsm | Assignee: | Ala Hino <ahino> | |
Status: | CLOSED ERRATA | QA Contact: | Kevin Alon Goldblatt <kgoldbla> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.1.4 | CC: | ahino, bcholler, bzlotnik, kshukla, lsurette, michal.skrivanek, ratamir, rbalakri, Rhev-m-bugs, rhv-bugzilla-bot, srevivo, tnisan, ycui, ykaul | |
Target Milestone: | ovirt-4.2.0 | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | vdsm-4.20.8 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1509614 (view as bug list) | Environment: | ||
Last Closed: | 2018-05-15 17:51:57 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: | 1509614 |
Description
Koutuk Shukla
2017-09-05 16:03:37 UTC
according to pathces, fixes are in vdsm not engine, changing component to add to right ET. INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Project 'vdsm'/Component 'ovirt-engine' mismatch] For more info please contact: rhv-devops Tested with the following code: -------------------------------- ovirt-engine-4.2.0-0.6.el7.noarch vdsm-4.20.9-1.el7ev.x86_64 Verified with the following scenario: ----------------------------------------------------- 1.Create Vm with 5 disks 2.Create snapshot s1 3.Start VM add data to disks 4.Create snapshot s2 5.Delete snapshot s1 - all snapshot is merged correctly, all disk snapshots are removed, no "No such drive error" reported 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/RHEA-2018:1489 BZ<2>Jira Resync |