+++ This bug was initially created as a clone of Bug #1679882 +++ Description of problem: ====================== On a RHHI 1.6 setup,restarting a powered off vm fails to come up. This was seen repeatedly in the environment, after powering off the vm's. Version-Release number of selected component (if applicable): ============================================================ ovirt-engine-4.3.0.4-0.1.el7.noarch glusterfs-3.12.2-43.el7rhgs.x86_64 rhvh-4.3.0.4-0.20190220.0+1 How reproducible: ================ 2/2 Steps to Reproduce: ================== 1.Deploy a RHHI 1.6 (RHV 4.3 + RHGS 3.4.3 ) 2.Poweroff a vm 3.Start the vm Actual results: ============== The vm fails to come up Expected results: =============== The vm should start immediately Additional info: =============== Just a small history on the setup, I actually performed a major upgrade from 4.2 (rhv 4.2.8) to 4.3 (rhv 4.3.0.4-0) before doing this test. So the vm's created are based out of 4.2.8. --- Additional comment from bipin on 2019-02-22 06:49:41 UTC ---
Moving this to MODIFIED as dependent bug is in MODIFIED
Moving the bug to verified based on the below results. Components tested in: ==================== vdsm-4.30.10-1.el7ev.x86_64 rhvh-4.3.0.5-0.20190305.0+1 Steps: ===== 1.Created a RHHI setup with RHV 4.2 hypervisors 2.Create vm's and start IO 3.Upgrade to rhv 4.3 4.Poweroff/reboot the vm's created earlier Output: ====== [root@rhsqa-123 91d34e11-5783-4b52-8484-5f2ac8e7d4cc]# ls -lt total 65684 -rw-rw----. 2 vdsm kvm 67108864 Mar 13 13:13 7d1da819-fee7-41b1-a07e-21b8ffd922d6 -rw-rw----. 2 vdsm kvm 1048576 Mar 13 12:54 7d1da819-fee7-41b1-a07e-21b8ffd922d6.lease -rw-r--r--. 2 vdsm kvm 320 Mar 13 12:54 7d1da819-fee7-41b1-a07e-21b8ffd922d6.meta Could see the owner of the image as vdsm.
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:1121