Description of problem: 1. Create a VM 2. Upload a big ISO to a Data Domain (yay!) 3. Attach the ISO to the VM 4. Start the VM The upload did not finish yet. But the VM is running with it attached. Version-Release number of selected component (if applicable): ovirt-engine-4.2.3.5-1.el7.centos.noarch How reproducible: 100% Actual results: VM started with some corrupted ISO Expected results: Something else? warn user/block start/detach iso
This is actually not a regression, you could have started a VM with a partially copied/uploaded file from an ISO domain, however, given the better control we have over data domains this can be fixed for data domains only
(In reply to Tal Nisan from comment #1) > This is actually not a regression, you could have started a VM with a > partially copied/uploaded file from an ISO domain, however, given the better > control we have over data domains this can be fixed for data domains only I'd imagine that during upload the disk should be locked, and we should not allow attaching locked ISOs, no?
(In reply to Yaniv Kaul from comment #2) > (In reply to Tal Nisan from comment #1) > > This is actually not a regression, you could have started a VM with a > > partially copied/uploaded file from an ISO domain, however, given the better > > control we have over data domains this can be fixed for data domains only > You are right, it happens on the old ISO domains too. This was just me playing with the new features. I see this is proposed to 4.2, the is no downstream ticket attached so I assume 4.3 is fine. Severity is set to low. > I'd imagine that during upload the disk should be locked, and we should not > allow attaching locked ISOs, no? That's what I expected.
(In reply to Yaniv Kaul from comment #2) > (In reply to Tal Nisan from comment #1) > > This is actually not a regression, you could have started a VM with a > > partially copied/uploaded file from an ISO domain, however, given the better > > control we have over data domains this can be fixed for data domains only > > I'd imagine that during upload the disk should be locked, and we should not > allow attaching locked ISOs, no? Yes, exactly, since we have ISO on data domain we can mark them as locked as opposed to ISOs on an ISO domain on which we have no information about the ISO
Verified on 4.2.4.1-0.1. Checked original scenario & saw that VM can't be started while upload is in progress(disk locked). Checked also that after the ISO disk upload is done that the VM can indeed be started with the same ISO disk in VM boot option as CD.
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 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.