Bug 1895697

Summary:	Modifying disk allocation target domain in the clone modal doesn't reflect on the cloned VM
Product:	[oVirt] ovirt-engine	Reporter:	Tamir <tamir>
Component:	BLL.Virt	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tamir <tamir>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4.3.10	CC:	ahadas, bugs, mavital, michal.skrivanek
Target Milestone:	ovirt-4.4.4	Keywords:	Regression
Target Release:	4.4.4.2	Flags:	pm-rhel: ovirt-4.4+ pm-rhel: blocker?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.4.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-21 12:35:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tamir 2020-11-08 13:53:23 UTC

Description of problem:
When I clone any VM with disks and in the clone modal under "resource allocation" -> "Disk Allocation", I change the disk's target to another domain, the change doesn't reflect on the cloned VM.

Version-Release number of selected component (if applicable):
RHV 4.4.3-13 (ovirt-engine.noarch 4.4.3.10-0.1.el8ev)
RHEL 8.3 x86 hosts and engine.
vdsm.x86_64 4.40.35.1-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. Clone the VM and in the clone modal change the disk's target in the resource allocation tab.
5. Check the cloned VM disk is located in the expected target domain.

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 cloned VM was created.
5. The cloned VM disk isn't located at the expected target domain, it is located at the same domain as the base VM.

Expected results:
Steps 1-4 were executed as expected.
5 - The cloned VM's disk should be located at the target domain we set in the resource allocation tab.

Additional info:

Comment 1 RHEL Program Management 2020-11-27 15:53:50 UTC

This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Tamir 2020-11-29 09:10:10 UTC

Verified on RHV 4.4.4-3. All looks good to me.

Env:
  - Engine instance with RHV 4.4.4-3 (ovirt-engine-4.4.4.2-0.1.el8ev.noarch) and RHEL 8.3 installed.
  - 2 hosts with RHV 4.4.4-3 and RHEL 8.3, both hosts with 4.40.38-1.el8ev.

Steps:
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. Clone the VM and in the clone modal change the disk's target in the resource allocation tab.
5. Check the cloned VM disk is located in the expected target domain.


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 cloned VM was created.
5. The cloned VM disk is located at the expected target domain.

Comment 3 Sandro Bonazzola 2020-12-21 12:35:49 UTC

This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.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.