Bug 1952321
| Summary: | There is failed cloning message when cloning VM with shareable direct lun attached | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Qin Yuan <qiyuan> | ||||||
| Component: | General | Assignee: | Shmuel Melamud <smelamud> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Qin Yuan <qiyuan> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.4.6.4 | CC: | ahadas, bugs | ||||||
| Target Milestone: | ovirt-4.5.0 | Flags: | pm-rhel:
ovirt-4.5?
|
||||||
| Target Release: | 4.5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-4.5.0 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2022-04-20 06:33:59 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1774279 [details]
engine.log
What should be a correct behaviour in this case? Currently, in the UI all LUN disks are filtered out, but CloneVmCommand allows shareable ones (while not handling them correctly). Theoretically, it is possible to support shareable LUN disks in cloning (for example, attaching them to the clone), but supporting LUN disks in the clone VM dialog in the UI will require a significant effort. how do we handle this when creating a template out of a VM with a shareable LUN? I'd expect clone VM to behave similarly Discussed offline - those sharable LUNs are filtered-out when creating a template from vm, we can do the same for clone-VM maybe it's better to assign the sharable LUN for the cloned VM but it will require massive changes Verified with: ovirt-engine-4.5.0.2-0.7.el8ev.noarch Steps: The same steps as in the bug description. Results: 1. The shareable direct lun disk isn't attached to the cloned VM. 2. There is finished cloning message when cloning completes. This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.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. |
Created attachment 1774278 [details] Screenshot of failed cloning message Description of problem: When cloning VM with shareable direct lun attached, a failed cloning message pops up during cloning, though the cloning process is still in progress. Cloning succeeds at last, but there is no finished cloning message which should pop up when cloning is completed. Version-Release number of selected component (if applicable): ovirt-engine-4.4.6.5-447.gd80dda7.9.el8ev.noarch How reproducible: 100% Steps to Reproduce: 1. Create a VM(used latest-rhel-guest-image-8.3-infra template) 2. Create a direct lun disk, Storage Type iSCSI, shareable checked. 3. Attach the shareable direct lun to the VM, interface VirtIO-SCSI, Activate Disk checked. 4. Clone the VM, monitor popping up messages. Actual results: 1. A failed cloning message pops up during cloning though cloning process is still in process. The message is like "Failed Creating VM clone_vm_with_shareable_lun as a clone of VM vm_with_shareable_lun". 2. Cloning VM succeeds at last, but there is no finished cloning message which should be like "Finished Creating VM clone_vm_with_shareable_lun as a clone of VM vm_with_shareable_lun". Expected results: 1. There shouldn't have failed cloning message when cloning is still working and succeeds at last. 2. There should have finished cloning message when cloning is completed. Additional info: