Description of problem: When import VM (that was exported) from export domain, the new VM is being created but the original VM has another disk with the same id as the original one. The first disk (that was created with the VM) is preallocated on iscsi domain. The second disk (that was added during the import VM) is thin provisioned on the same iscsi domain. Version-Release number of selected component (if applicable): ovirt-engine-4.3.5.4-0.1.el7.noarch How reproducible: always Steps to Reproduce: 1. Create a VM with a preallocated disk on iscsi domain 2. Take snapshot 3. Export the VM to export domain 4. Import the VM with a new name using the same iscsi domain Actual results: The original VM has extra disk with the same id as the original one Expected results: Even though the VM has the extra disk, it shouldn't be with the same id Additional info:
Did you choose the "Import as Clone" option?
(In reply to Tal Nisan from comment #1) > Did you choose the "Import as Clone" option? The "clone" checkbox is checked and disabled. So yes.
Created attachment 1603791 [details] export_import_vm See attached capture
This issue is regression, occurred first in 4.3.5 and it really looks bad(another disk is added to original VM with thin provision). This is 100% reproducible manually. Raising to high priority, consider fixing in 4.3.7.
Export domain will be removed in 4.4, no need to fix this
(In reply to Avihai from comment #4) > This issue is regression, occurred first in 4.3.5 and it really looks > bad(another disk is added to original VM with thin provision). > This is 100% reproducible manually. > > Raising to high priority, consider fixing in 4.3.7. Note, this is not another disk, it's the snapshot just the snapshot image, because its "active" column is has been changed to true for some reason. This can be worked around by changing it back to "false".
(In reply to Tal Nisan from comment #5) > Export domain will be removed in 4.4, no need to fix this Reopening as we now realize that export domain is here to stay in 4.4. Also this is a clear regression(since 4.3.5), how much effort will it take to fix this bug? (In reply to Benny Zlotnik from comment #6) > Note, this is not another disk, it's the snapshot just the snapshot image, > because its "active" column is has been changed to true for some reason. > This can be worked around by changing it back to "false". The user sees the original VM has extra disk with the same id as the original one -> this looks bad. Can you please add the suggested work around in the code and fix this issue? Original scenario 1. Create a VM with a preallocated disk on iscsi domain 2. Take snapshot 3. Export the VM to export domain 4. Import the VM with a new name using the same iscsi domain Actual results: The original VM has extra disk with the same id as the original one
13:23:22 < vjuranek> lsvaty|gchat: jmacku lleistne I just went (by accident) over this isseu: https://bugzilla.redhat.com/show_bug.cgi?id=1734409 ... may be related to the issue we discussed in the morning (maybe even exactly the issue) that would mean it is blocking currently 4.4 QE full Automation (adding keyword) Adding info as it is worth considering
tried with REST api, after exporting the vm, the endpoint returns one disk. but in UI I see there are two disks.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'ovirt-engine-4.4.0' doesn't contain patch 'https://gerrit.ovirt.org/105738'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.4.0 For more info please contact: infra
I verified this BZ following those steps: 1. Create a VM with a preallocated disk on iscsi domain. Not from template. Without OS. 2. Take snapshot (VM down) 3. Export the VM to export domain 4. Import the VM with a new name using the same iscsi domain. This is done twice since i wasnt sure which disk format should be used for this (thin / preallocated) Actual results: Both,The original and imported VM DO NOT have extra disk. Only one (original disk) I also verified this using API and looking at diskattachments per each VM (ORIGINAL and imported).
Ahmed, since i am not the reporter of the BZ and my familiarity with this BZ is from reading it only, please see my verification steps and consider them as a verification or not. So i could change the status of this bz to 'verified.'
Hi Ilan, the steps in comment #13 are correct! but can be done once or see the first comment as Yossi mentioned. the expected result is after importing the VM, you will see one disk for the VM, not two disks
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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.