+++ This bug was initially created as a clone of Bug #1575913 +++ 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: --- Additional comment from Michal Skrivanek on 2018-05-09 04:11:33 EDT --- seems it's like that for a long time --- Additional comment from Michal Skrivanek on 2018-07-18 02:27:52 EDT ---
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops
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.
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, 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/RHEA-2019:1085
sync2jira