Description of problem: 'Next Run configuration snapshot' is created for a VM when a configuration change was done for it while it's running. This snapshot is part of the VM snapshots collection and can be picked for operations like clone VM from snapshot. In the case of clone VM from this snapshot, a new VM is created but it's missing VM devices like disks. Version-Release number of selected component (if applicable): ovirt-engine-4.2.3.4-0.1.el7.noarch How reproducible: Always Steps to Reproduce: 1. Create a VM 2. Start the VM 3. Edit the VM, like change memory or HA conf Actual results: The VM snapshots collection now has 'Next Run configuration snapshot' Expected results: Not sure if 'Next Run configuration snapshot' is exposed by intention and if so, all snapshots operations should not be allowed for it Additional info:
seems it's like that for a long time
*** Bug 1601713 has been marked as a duplicate of this bug. ***
This will not make it in a reasonable time. Please re-open if you still feel this should be fixed
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
Verified on: virt-engine-4.3.2.1-0.0.master.20190310172919.git0b3fbad.el7 qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 vdsm-4.40.0-59.git5533158.el7.x86_64 libvirt-client-4.5.0-10.el7_6.4.x86_64 Verification steps: 1) Run VM 2) Edit VM -> Change memory or HA 3) Check that you have delta icon on the VM and 'Next Run configuration snapshot' is created under VM snapshots 4) Verify that clone VM, Delete and Make template options are not available.
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 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.