Red Hat Bugzilla – Bug 1575922
RHVH 4.2 upgrade failed from 4.1 wrapper to wrapper
Last modified: 2018-07-10 18:36:52 EDT
Description of problem: Wrapper to Wrapper upgrade failed. Installed the released version rhvh-4.1-0.20180314.0(el7.4), updated the host to rhvh-4.1-0.20180410.0(el7.5), then updated the host to rhvh-4.2.3.0-0.20180507.0(el7.5), failed to upgrade by yum update. # yum update <snip> Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : redhat-virtualization-host-image-update-4.2-20180507.0.el7_5.noarch 1/3 warning: %post(redhat-virtualization-host-image-update-4.2-20180507.0.el7_5.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package redhat-virtualization-host-image-update-4.2-20180507.0.el7_5.noarch Erasing : redhat-virtualization-host-image-update-placeholder-4.1-10.5.el7.noarch 2/3 Cleanup : redhat-virtualization-host-image-update-4.1-20180410.1.el7_5.noarch 3/3 warning: file /usr/share/redhat-virtualization-host/image/redhat-virtualization-host-4.1-20180410.1.el7_5.squashfs.img.meta: remove failed: No such file or directory warning: file /usr/share/redhat-virtualization-host/image/redhat-virtualization-host-4.1-20180410.1.el7_5.squashfs.img: remove failed: No such file or directory Uploading Package Profile Verifying : redhat-virtualization-host-image-update-4.2-20180507.0.el7_5.noarch 1/3 Verifying : redhat-virtualization-host-image-update-4.1-20180410.1.el7_5.noarch 2/3 Verifying : redhat-virtualization-host-image-update-placeholder-4.1-10.5.el7.noarch 3/3 Installed: redhat-virtualization-host-image-update.noarch 0:4.2-20180507.0.el7_5 Replaced: redhat-virtualization-host-image-update-placeholder.noarch 0:4.1-10.5.el7 Complete! </snip> Version-Release number of selected component (if applicable): a. rhvh-4.1-0.20180314.0 b. rhvh-4.1-0.20180410.0 c. rhvh-4.2.3.0-0.20180507.0 How reproducible: 100% Steps to Reproduce: 1. Installed rhvh-4.1-0.20180314.0 successful. 2. Reboot after installation 3. Yum update to rhvh-4.1-0.20180410.0 successful. 4. Reboot after the update. 5. Login rhvh-4.1-0.20180410.0 6. Check nodectl status and imgbased # nodectl info layers: rhvh-4.1-0.20180314.0: rhvh-4.1-0.20180314.0+1 rhvh-4.1-0.20180410.0: rhvh-4.1-0.20180410.0+1 bootloader: default: rhvh-4.1-0.20180410.0+1 entries: rhvh-4.1-0.20180410.0+1: index: 0 title: rhvh-4.1-0.20180410.0 kernel: /boot/rhvh-4.1-0.20180410.0+1/vmlinuz-3.10.0-862.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=rhvh/swap rd.lvm.lv=rhvh/rhvh-4.1-0.20180410.0+1 rhgb quiet LANG=en_US.UTF-8 img.bootid=rhvh-4.1-0.20180410.0+1" initrd: /boot/rhvh-4.1-0.20180410.0+1/initramfs-3.10.0-862.el7.x86_64.img root: /dev/rhvh/rhvh-4.1-0.20180410.0+1 rhvh-4.1-0.20180314.0+1: index: 1 title: rhvh-4.1-0.20180314.0 kernel: /boot/rhvh-4.1-0.20180314.0+1/vmlinuz-3.10.0-693.21.1.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=rhvh/rhvh-4.1-0.20180314.0+1 rd.lvm.lv=rhvh/swap rhgb quiet LANG=en_US.UTF-8 img.bootid=rhvh-4.1-0.20180314.0+1" initrd: /boot/rhvh-4.1-0.20180314.0+1/initramfs-3.10.0-693.21.1.el7.x86_64.img root: /dev/rhvh/rhvh-4.1-0.20180314.0+1 current_layer: rhvh-4.1-0.20180410.0+1 # imgbase layout rhvh-4.1-0.20180314.0 +- rhvh-4.1-0.20180314.0+1 rhvh-4.1-0.20180410.0 +- rhvh-4.1-0.20180410.0+1 # nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK 7. Yum update to version rhvh-4.2.3.0-0.20180507.0 8. Check # imgbase w You are on rhvh-4.1-0.20180410.0+1 # imgbase layout rhvh-4.1-0.20180314.0 +- rhvh-4.1-0.20180314.0+1 rhvh-4.1-0.20180410.0 +- rhvh-4.1-0.20180410.0+1 rhvh-4.2.3.0-0.20180507.0 +- rhvh-4.2.3.0-0.20180507.0+1 9. Reboot, still enter into the rhvh-4.1-0.20180410.0, NOT rhvh-4.2.3.0-0.20180507.0 Actual results: After step 7, update failed. Expected results: 4.1 wrapper to 4.2 upgrades successfully. Additional info:
Created attachment 1433115 [details] sosreport after wrapper to wrapper upgrade.
This bug is fixed in redhat-virtualization-host-4.2-20180508.0. Test version: a. rhvh-4.1-0.20180314.0 b. rhvh-4.1-0.20180410.0 c. rhvh-4.2.3.0-0.20180508.0 imgbased-1.0.16-0.1.el7ev.noarch Test steps: Same as comment 0 Test results: 4.1 wrapper to 4.2 upgrades successfully. So change the status to VERIFIED.
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.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.
*** Bug 1576915 has been marked as a duplicate of this bug. ***
imgbased-1.0.16 has not been released in oVirt 4.2.3, reopening and moving to 4.2.4.
Need to update the kcs. Here the problem is with insights. The logs will show errors with rsync /etc. To resolve, "cp -rv /etc/redhat-access-insights/* /etc/insights-client"
Test version: a. rhvh-4.1-0.20180314.0 b. rhvh-4.1-0.20180410.0 c. redhat-virtualization-host-4.2-20180530.1 imgbased-1.0.17-0.1.el7ev.noarch Test steps: Same as comment 0 Test results: 4.1 wrapper to 4.2 upgrades successfully. So change the status to VERIFIED.
@Ryan can you take a look as well? I have a customer who can't boot to RHV 4.2 image, he installed rhvh-4.2.3.0-0.20180518.0: I have found on RHV-M in var/log/ovirt-engine/host-deploy that an installation failed for post-installation script: \nwarning: %post(redhat-virtualization-host-image-update-4.2-20180518.2.el7_5.noarch) scriptlet failed, exit status 1\n There is no imgbased.log so I can't check more details + a customer was quite disappointed and didn't have time so he reinstalled from ISO
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/RHSA-2018:1820