Created attachment 1661963 [details] engine.log Description of problem: According to the engine.log it looks like VM is created by clone action, but it is really not Version-Release number of selected component (if applicable): http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-18 How reproducible:100% Steps to Reproduce: 1. Select existent VM in Compute/Virtual Machines window. The existent VM was created on the base of oficial latest-rhel-guest-image-8.1-infra template. Select Clone VM, insert the new name for the VM. Actual results: as result you got error - 2020-02-09 11:12:38,423+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-17) [75cc5844] EVENT_ID: USER_FAILED_ADD_VM(57), Failed to create VM test (User: admin@internal-authz). Then you see notification in engine.log and in the Events that says it succeeds 2020-02-09 11:13:16,764+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-23) [] EVENT_ID: USER_ADD_VM_FINISHED_SUCCESS(53), VM test creation has been completed. The VM is not created really . it is seen neither in the UI window nor in get VMs response. Expected results: VM cloned. Additional info:
I could reproduce locally the problem when cloning VM created from a template. This was related to the fact that the template of a cloned VM is set to "Blank". https://github.com/oVirt/ovirt-engine/commit/9957082031a1352cc7437298d429a825c43fb4c2 However, for me, the UI correctly displayed a dialog explaining the problem (With message: The requested template doesn't belong to the same base template as the original template.).
Verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-23 The original problem (VM not cloned) is solved. There is a minor issue in UI: upon click 'Clone' for the selected desktop VM , the open Edit window for the cloned VM automatically sets the cloned VM as a Server. this could be changed by the user if he noticed. please let me know if we want to leave it this way.
The new VM has to be configured the same way as the original one - so this should be fixed. I'll look into it.
so, I verify this one and will open a new one for webui
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days