Bug 1696245

Summary:	[RFE] Allow full customization while cloning a VM
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Abhishekh Patil <abpatil>
Component:	ovirt-engine	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED ERRATA	QA Contact:	Tamir <tamir>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.8	CC:	ljelinko, michal.skrivanek, mtessun, rdlugyhe
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature, Reopened
Target Release:	---	Flags:	lsvaty: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-4.4.0-29	Doc Type:	Enhancement
Doc Text:	Previously, while cloning a virtual machine, you could only edit the name of the virtual machine in the Clone Virtual Machine window. With this enhancement, you can fully customize any of the virtual machine settings in the Clone Virtual Machine window. This means, for example, that you can clone a virtual machine into a different storage domain.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-04 13:16:58 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:

Description Abhishekh Patil 2019-04-04 12:08:17 UTC

Proposed title of this feature request:

Allow user to create disk from different storage domain while cloning a VM. 

Currently, while cloning a VM, disk is created in the same storage domain in which original VM's disk resides.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.8


How reproducible:
[100%]

Steps to Reproduce:
1. Create a VM with a disk on storage domain
2. Clone The VM


Actual results:
Cloned VM's disk is created in the same storage domain

Expected results:
User should be able to create the disk from different storage domain while cloning a VM.

Comment 2 RHV bug bot 2019-12-13 13:16:27 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 3 RHV bug bot 2019-12-20 17:45:56 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 4 RHV bug bot 2020-01-08 14:49:47 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 5 RHV bug bot 2020-01-08 15:18:22 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 6 RHV bug bot 2020-01-24 19:51:37 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 9 Lukas Svaty 2020-04-16 10:36:13 UTC

Closing low severity bugs, based on QE capacity, if you would like to still verify this issue please reopen.

Comment 10 Lucia Jelinkova 2020-04-16 13:16:42 UTC

I think this functionality should be tested as it can break cloning VM from UI.

Comment 11 Tamir 2020-07-05 05:47:55 UTC

Tested the RFE on RHV 4.4.1-5 (engine and hosts RHEL 8) using the tests attached (Polarion).

Changing to verified.

Comment 19 errata-xmlrpc 2020-08-04 13:16:58 UTC

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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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/RHSA-2020:3247