+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1635942 +++ ====================================================================== Description of problem: When cloning a VM that has a Direct LUN attached, the UI immediately shows the clone failed (task is red, failed), but the task is actually running just fine and later it finished, unlocking the VM. Version-Release number of selected component (if applicable): ovirt-engine-4.2.6.4-1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Create a VM, attach a Direct LUN Disk 2. Clone the VM Actual results: - Clone succeeds - UI shows task as failed, but its actually running Expected results: - Clone succeeds - UI shows task running, then completes when the disk copy finished. Additional info: 2018-10-04 12:53:08,891+10 WARN [org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] (default task-4) [715bb46a] Validation of action 'AttachDiskToVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__ATTACH_ACTION_TO,VAR__TYPE__DISK,VALIDATION_DISK_INTERFACE_NOT_NULL,$message VALIDATION_DISK_INTERFACE_NOT_NULL,$payload [Ljava.lang.Class;@47f46a48,$groups [Ljava.lang.Class;@232dfdbb,ACTION_TYPE_FAILED_ATTRIBUTE_PATH,$path diskVmElement.diskInterface,$validatedValue null (Originally by Germano Veit Michel)
Any symptoms from bug 1623379? (Originally by michal.skrivanek)
(In reply to Michal Skrivanek from comment #1) > Any symptoms from bug 1623379? I just blew up my test setup to do some more testing for bug 1620314 (unrelated), so cant check ui.log But no, there were no UI exceptions, everything works fine, except the UI shows the task as failed immediately and the engine throws that warning. If one waits the clone creation actually finished, the VM is unlocked and everyone is happy. I can test again if required... after I rebuild this =D (Originally by Germano Veit Michel)
The clone VM succeeded and the UI shows it. The message from the task running(in green color): "Creating VM shir_clone_vm as a clone of VM shirVM" ovirt-engine-4.3.0-0.0.master.20181101091940.git61310aa.el7.noarch (Originally by Shir Fishbain)
The clone VM succeeded and the UI shows it. The message from the task running(in green color): "Creating VM shirClone as a clone of VM shirVM" ovirt-engine-4.2.8-0.0.master.20181119152157.gita72a684.el7.noarch vdsm-4.20.43-4.gitb76af64.el7.x86_64 (Originally by Shir Fishbain)
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops (Originally by rhv-bugzilla-bot)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0121