Bug 1429246
| Summary: | VMs imported from libvirt have no cdrom device | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Chris Boot <redhat> |
| Component: | General | Assignee: | Shmuel Melamud <smelamud> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0.3 | CC: | bugs, mavital, michal.skrivanek, nsimsolo, redhat, tjelinek |
| Target Milestone: | ovirt-4.2.2 | Flags: | rule-engine:
ovirt-4.2+
|
| Target Release: | 4.2.1.2 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.1.2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-27 07:22:33 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: | |||
|
Description
Chris Boot
2017-03-05 21:51:23 UTC
Yaniv, the fix is in 4.2 already. Verification version: rhvm-4.2.3.2-0.1.el7 vdsm-4.20.26-1.el7ev.x86_64 libvirt-client-3.9.0-14.el7_5.2.x86_64 qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64 sanlock-3.6.0-1.el7.x86_64 Verification scenario: 1. Prepare KVM environment with RHEL7 VM and CDROM with SATA disk bus. Attach ISO file to cdrom. 2. From RHV environment, Import RHEL 7 VM from KVM env. 3. Verify import succeeded. - Browse Webadmin -> Compute -> VMs -> Click on imported VM -> VM devices: Verify CDROM device is listed as plugged and managed. - Run imported VM, attach ISO file to VM CD, open VM console and verify CD is attached with ISO file. 4. Repeat steps 1-3 for RHEL7 VM with IDE CDROM. 5. Repeat stpes 1-3 for RHEL 7 with iSCSI CDROM. 6. Repeat steps 1-3 for Windows VM with SATA CDROM. 7. cross effect test, import VM from VMware with CD and verify CD device exist after import (steps 3 expected results). This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |