Created attachment 1724028 [details] Added logs, the logs in the host log folder are related to the host with the running VM Created attachment 1724028 [details] Added logs, the logs in the host log folder are related to the host with the running VM Description of problem: When cloning a running VM, the cloned VM fails to be created. Added logs. Version-Release number of selected component (if applicable): RHV 4.4.3-10 (ovirt-engine.noarch 4.4.3.8-0.1.el8ev) RHEL 8.3 x86 hosts and engine. vdsm.x86_64 4.40.35-1.el8ev on the hosts. How reproducible: 100% Steps to Reproduce: 1. Create a 4.5 data center and a 4.5 cluster. 2. Install the host and create a new NFS storage domain. 3. Create a VM with a disk and wait for its creation. 4. Run the VM. 5. Clone the VM. Actual results: 1. The 4.5 data center and the 4.5 cluster were created. 2. The host was installed and the NFS storage domain was created. 3. The VM with the disk was created. 4. The VM is running. 5. The VM clone has failed after 30 minutes. Expected results: 1-4 steps are as expected. 5. The VM should have been cloned. Additional info:
I verified the bug on RHV 4.4.3-13. All looks good to me. Env: - Engine instance with RHV 4.4.3-13 (ovirt-engine-4.4.3.10-0.1.el8ev) and RHEL 8.3 installed. - 3 hosts with RHV 4.4.3-13 and RHEL 8.3, vdsm-4.40.35.1-1.el8ev Steps: In Admin Portal: 1. Create a 4.5 data center and a 4.5 cluster. 2. Install the host and create a new NFS storage domain. 3. Create a VM with a disk and wait for its creation. 4. Run the VM. 5. Clone the VM. Results (As Expected): 1. The 4.5 data center and the 4.5 cluster were created. 2. The host was installed and the NFS storage domain was created. 3. The VM with the disk was created. 4. The VM is running. 5. The VM clone has cloned successfully.
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.