Bug 1575777
Summary: | RHV import fails if VM has an unreachable floppy defined | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Javier Coscia <jcoscia> | |
Component: | vdsm | Assignee: | Tomáš Golembiovský <tgolembi> | |
Status: | CLOSED ERRATA | QA Contact: | Nisim Simsolo <nsimsolo> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 4.1.11 | CC: | ebenahar, lsurette, michal.skrivanek, nsimsolo, rdlugyhe, sgoodman, srevivo, ycui | |
Target Milestone: | ovirt-4.3.0 | Keywords: | Rebase, ZStream | |
Target Release: | 4.3.0 | Flags: | lsvaty:
testing_plan_complete-
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | v4.30.3 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, a floppy drive in a virtual machine could prevent the virtual machine from being imported. In the current release, floppy drives are ignored during import.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1576675 (view as bug list) | Environment: | ||
Last Closed: | 2019-05-08 12:36:02 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1641536 | |||
Bug Blocks: | 1576675 |
Description
Javier Coscia
2018-05-07 21:36:56 UTC
please also check the new wrapper Not sure if I did it right but I've added the "or device == 'floppy'" on lib/vdsm/v2v.py https://gerrit.ovirt.org/#/c/90981/ Although I see there's a 'Merge Conflict' on it, not sure what could be wrong Verified_upstream: ovirt-engine-4.3.0-0.0.master.20181023141116.gitc92ccb5.el7 vdsm-4.30.1-25.gitce9e416.el7.x86_64 libvirt-client-4.5.0-10.el7.x86_64 qemu-kvm-common-ev-2.10.0-21.el7_5.7.1.x86_64 virt-v2v-1.38.2-12.el7.x86_64 Verification scenario: 1. Import KVM VM with unreachable path. 2. Verify VM imported successfully and VM parameters are equal to source VM parameters.. Run VM and verify VM is running properly. 3. Repeat steps 1-2 foe Xen VM. 4. Repeat steps 1-2 for VMware VM. 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-2019:1077 sync2jira sync2jira |