This bug tracks the first part of https://bugzilla.redhat.com/show_bug.cgi?id=1819299#c8 - the ownership on memory dump volumes changes upon restoring the memory state and consequently, further attempts to restore the memory state from the same volumes fail.
Moving to ON_QA since we use RHEL 8.3 with RHV 4.3.3. The version needed is >= libvirt-daemon-6.6.0-2.module+el8.3.0+7567+dc41c0a9.x86_64
Verified with: - ovirt-engine-4.4.3.6-0.13.el8ev.noarch - vdsm-4.40.33-1.el8ev.x86_64 - libvirt-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64 Verification steps: 1. Create and start a VM 2. Create a snapshot with memrory and verify that the memory volume set with vdsm:kvm as owner:group 3. Preview and commit the snapshot 4. Start and shutdown the VM 5. Make sure the owner:group remain vdsm:kvm 6. Re-preview and commit the snapshot 7. Start the VM and make sure it up and running. Result: - owner:group remains vdsm:kvm after section 4, and the VM is up and running as expected after section 7.
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.