Bug 1632068
Summary: | Cannot import VM from KVM without ISO Domain active | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Germano Veit Michel <gveitmic> |
Component: | BLL.Virt | Assignee: | Steven Rosenberg <srosenbe> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.6 | CC: | ahadas, bugs, lrotenbe, mavital, nsimsolo, ryasuoka, srosenbe |
Target Milestone: | ovirt-4.4.3 | Flags: | pm-rhel:
ovirt-4.4+
rbarry: ovirt-4.5? pm-rhel: planning_ack+ pm-rhel: devel_ack+ mavital: testing_ack+ |
Target Release: | 4.4.3.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.4.3.2 | Doc Type: | Bug Fix |
Doc Text: |
Cause: An iso file is added as a disk when no iso Storage Domain exists and the user performs a KVM import.
Consequence: The KVM import fails because a virtio iso file is detected, but the iso Storage Domain is not.
Fix: Added virtio iso file validation by verifying the import is not a KVM import.
Result: The KVM import succeeds.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-11 06:41:45 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
Germano Veit Michel
2018-09-24 03:39:26 UTC
Likely to be fixed as a side effect of the ISO domain -> data domain changes Still happening on ovirt-engine-4.3.6.7-1.el7.noarch. It's annoying to have to add an ISO domain to import VMs from KVM. We should not require virtio at all when importing from libvirt as we don't modify the VM but only copy its disks. I was able to import a KVM on a clean install without an ISO Domain on 4.4. Maybe we can retest this with the current version? 4.2 is no longer supported. (In reply to Steven Rosenberg from comment #4) > I was able to import a KVM on a clean install without an ISO Domain on 4.4. > Maybe we can retest this with the current version? 4.2 is no longer > supported. Sorry for the delay, I was on leave. If you say it is working on 4.4 then the bug can be closed after passing QE. But do you know what fixed it? The code triggering the error still seems to be in 4.4: https://github.com/oVirt/ovirt-engine/blob/14967178f54e1017f379a07587d7c27b228eeaf1/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/exportimport/ImportVmFromExternalProviderCommand.java#L182 Would be nice to know what fixed it to attach to the BZ. Steven, could it be that you didn't have the virtio ISO at all on your data center? To make sure it doesn't happen anymore we need to import from KVM in an environment that has the virtio ISO on some data domain and no ISO domain defined. It's working for me on 4.4 Beta refresh, so the initial problem described in comment #0 is now fixed. But I did not test with virtio ISO on data domain (4.4 guest tools iso not found on the customer portal) (In reply to Arik from comment #6) > Steven, could it be that you didn't have the virtio ISO at all on your data > center? > To make sure it doesn't happen anymore we need to import from KVM in an > environment that has the virtio ISO on some data domain and no ISO domain > defined. Right, and this fails easily on first try for me. In a simple minimal setup with: * No ISO Domain on the DC * virtio-win-1.9.12.iso uploaded to Data Domain Importing from KVM fails: 2020-07-23 11:01:28,070+10 WARN [org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand] (default task-15) [] Validation of action 'ImportVmFromExternalProvider' failed for user admin@internal-authz. Reasons: VAR__ACTION__IMPORT,VAR__TYPE__VM,ERROR_CANNOT_FIND_ISO_IMAGE_PATH Verified: ovirt-engine-4.4.3.5-0.5.el8ev vdsm-4.40.32-1.el8ev.x86_64 libvirt-daemon-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64 qemu-kvm-5.1.0-10.module+el8.3.0+8254+568ca30d.x86_64 KVM server: RHEL 7.9 qemu-kvm-1.5.3-175.el7.x86_64 Verification scenario: 1. Import KVM VM: with CD HW and CD media selected to RHV: without ISO domain and without virtio ISO drivers in data domain 2. Import KVM VM: With CD HW and CD media selected to RHV: without ISO domain and with virtio ISO drivers in data domain 3. Repeat steps 1-2, this time without CD media in KVM VM. 4. Import KVM VM: With CD HW and without media selected to RHV: with ISO domain 5. Import KVM VM: With CD HW and with media selected to RHV: with ISO domain 6. Run all imported VMs and verify VMs are running properly. This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 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. |