1. Proposed title of this feature request
Ability to clone a running VM
3. What is the nature and description of the request?
Add the ability to clone a vm while it's running through a simple GUI operations.
4. Why does the customer need this? (List the business requirements here)
It's not infrequent that a running VM, which cannot be stopped due to business continuity reasons, needs to be cloned. This operation cannot be performed in RHEV 3.5 directly.
5. How would the customer like to achieve this? (List the functional requirements here)
Right-click on a running VM in the Admin Portal and choose "Clone" from the contextual menu to fire the guided process that drives to the creation of a new cloned VM.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
a. Select a running VM in Admin portal.
b. right-click on it and verify that the "Clone" item is available in the contextual menu.
c. Select "Clone" and look the wizard start
d. follow the instructions of the wizard and verify that a new VM is created and that it's a clone of the original VM
e. The original running VM shouldn't be affected in its normal operations by the cloning process.
note it is possible today
you can create a live snapshot and clone a VM from there, then (ideally) live merge it back to the original image
This is how the RFE would be implemented internally anyway, though a convenient UI shortcut is desired
this is pending Command Coordination framework improvements, to be less cumbersome to use for chaining backend commands
This bug did not make it in time for 3.6 release, moving out
*** Bug 1226622 has been marked as a duplicate of this bug. ***
make sure to unblock in snapshot subtab as well, as requested in bug 1226622
open question is what to do with guest settings (NIC's MAC, etc).
with or without RAM.
*** Bug 1341856 has been marked as a duplicate of this bug. ***
we should use bug 1335642 to clear the new clone's config
Can we provide an Ansible script providing this functionality?
probably yes, but PM doesn't seem to be happy with it, so deferring to 4.2
We should try getting this done in 4.2.
As Ansible integration moves forward, maybe even an Ansible script that does the above described steps from comment 2 might suffice, but I believe we need a UI element that would trigger the Ansible scripts.
So what I personally think is an easy way to be consumed by customers is a way of having UI entries (like Clone VM) which trigger an Ansible script that is installed on the Manager that does all the steps and reports back to the UI (or creates some audit_log entries to verify its successful completion).
This can be done with Ansible scripts today. Is this a feasible approach.
Moran: Can you provide the Ansible plugins that are needed for that.
1. Snapshot the VM.
2. Clone from the Snapshot
3. Remove the Snapshot.
This will not be implemented in the RHV UI though, but can be implemented in CFME instead.
We agreed to remove the component RFEs from bugzilla. If you feel the component is incorrectly renamed please reach out.
1. Create a new command that is executed by the existing "Clone VM" UI action, if the target VM is running.
2. The command runs the following commands in order: create a VM snapshot, create a VM from the snapshot, delete the snapshot.
3. No changes are made in the newly created VM, besides assigning a new MAC address to NIC.
4. Memory image is not created.
5. REST API call is not implemented.
I tested the regular usage of the following feature on RHV 4.4.3-10 and I found an error that stopped me from testing further.
I opened the related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1891306
Also found another related low severity bug: https://bugzilla.redhat.com/show_bug.cgi?id=1891303
fixing bug 1891306 makes this feature usable
I verified the bug on RHV 4.4.3-13.
- Engine instance with RHV 4.4.3-13 (ovirt-engine-184.108.40.206-0.1.el8ev) and RHEL 8.3 installed.
- 3 hosts with RHV 4.4.3-13 and RHEL 8.3, vdsm-220.127.116.11-1.el8ev
I executed the tests I wrote in the "Polarion Requirement", most of the tests passed and I posted bugs for the issues I stumbled upon.
While the verification I stumbled upon those 3 bugs:
- Bug 1895695 - Modifying (add/remove/replace) NICs in the clone modal doesn't reflect on the cloned VM (https://bugzilla.redhat.com/show_bug.cgi?id=1895695)
- Bug 1895697 - Modifying disk allocation target domain in the clone modal doesn't reflect on the cloned VM (https://bugzilla.redhat.com/show_bug.cgi?id=1895697)
- Bug 1893540 - Cannot clone a suspended VM (https://bugzilla.redhat.com/show_bug.cgi?id=1893540)
Also it is worth noting that the fix for "Cloning modal doesn't close automatically when cloning is finished/failed" bug won't be released in this version and
there is no danger in closing the cloning modal manually anytime. (https://bugzilla.redhat.com/show_bug.cgi?id=1891303)
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 (RHV Manager (ovirt-engine) 4.4.z [ovirt-4.4.3] 0-day), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.