[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

Hi, i attached my /tmp/imgbased.log Sheers Oliver Am 02.07.2018 um 13:58 schrieb Yuval Turgeman <yuvalt(a)redhat.com&gt;: Looks like the upgrade script failed - can you please attach /var/log/imgbased.log or /tmp/imgbased.log ? Thanks, Yuval. On Mon, Jul 2, 2018 at 2:54 PM, Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > Yuval, can you please have a look? > > 2018-06-30 7:48 GMT+02:00 Oliver Riesener <Oliver.Riesener(a)hs-bremen.de&gt;: > >> Yes, here is the same. >> >> It seams the bootloader isn’t configured right ? >> >> I did the Upgrade and reboot to 4.2.4 from UI and got: >> >> [root@ovn-monster ~]# nodectl info >> layers: >> ovirt-node-ng-4.2.4-0.20180626.0: >> ovirt-node-ng-4.2.4-0.20180626.0+1 >> ovirt-node-ng-4.2.3.1-0.20180530.0: >> ovirt-node-ng-4.2.3.1-0.20180530.0+1 >> ovirt-node-ng-4.2.3-0.20180524.0: >> ovirt-node-ng-4.2.3-0.20180524.0+1 >> ovirt-node-ng-4.2.1.1-0.20180223.0: >> ovirt-node-ng-4.2.1.1-0.20180223.0+1 >> bootloader: >> default: ovirt-node-ng-4.2.3-0.20180524.0+1 >> entries: >> ovirt-node-ng-4.2.3-0.20180524.0+1: >> index: 0 >> title: ovirt-node-ng-4.2.3-0.20180524.0 >> kernel: /boot/ovirt-node-ng-4.2.3-0.20 >> 180524.0+1/vmlinuz-3.10.0-862.3.2.el7.x86_64 >> args: "ro crashkernel=auto rd.lvm.lv=onn_ovn-monster/ovirt-node-ng-4.2.3-0.20180524.0+1 >> rd.lvm.lv=onn_ovn-monster/swap rd.md.uuid=c6c3013b:027a9346:67dfd181:89635587 >> rhgb quiet LANG=de_DE.UTF-8 img.bootid=ovirt-node-ng-4.2.3 >> -0.20180524.0+1" >> initrd: /boot/ovirt-node-ng-4.2.3-0.20 >> 180524.0+1/initramfs-3.10.0-862.3.2.el7.x86_64.img >> root: /dev/onn_ovn-monster/ovirt-node-ng-4.2.3-0.20180524.0+1 >> ovirt-node-ng-4.2.1.1-0.20180223.0+1: >> index: 1 >> title: ovirt-node-ng-4.2.1.1-0.20180223.0 >> kernel: /boot/ovirt-node-ng-4.2.1.1-0. >> 20180223.0+1/vmlinuz-3.10.0-693.17.1.el7.x86_64 >> args: "ro crashkernel=auto rd.lvm.lv=onn_ovn-monster/ovir >> t-node-ng-4.2.1.1-0.20180223.0+1 rd.lvm.lv=onn_ovn-monster/swap >> rd.md.uuid=c6c3013b:027a9346:67dfd181:89635587 rhgb quiet >> LANG=de_DE.UTF-8 img.bootid=ovirt-node-ng-4.2.1.1-0.20180223.0+1" >> initrd: /boot/ovirt-node-ng-4.2.1.1-0. >> 20180223.0+1/initramfs-3.10.0-693.17.1.el7.x86_64.img >> root: /dev/onn_ovn-monster/ovirt-node-ng-4.2.1.1-0.20180223.0+1 >> current_layer: ovirt-node-ng-4.2.3-0.20180524.0+1 >> [root@ovn-monster ~]# uptime >> 07:35:27 up 2 days, 15:42, 1 user, load average: 1,07, 1,00, 0,95 >> >> Am 29.06.2018 um 23:53 schrieb Matt Simonsen <matt(a)khoza.com&gt;: >> >> Hello, >> >> I did yum updates on 2 of my oVirt 4.2.3 nodes running the prebuilt node >> platform and it doesn't appear the updates worked. >> >> >> [root@node6-g8-h4 ~]# yum update >> Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, >> : package_upload, product-id, search-disabled-repos, >> subscription- >> : manager >> This system is not registered with an entitlement server. You can use >> subscription-manager to register. >> Loading mirror speeds from cached hostfile >> * ovirt-4.2-epel: linux.mirrors.es.net >> Resolving Dependencies >> --> Running transaction check >> ---> Package ovirt-node-ng-image-update.noarch 0:4.2.3.1-1.el7 will be >> updated >> ---> Package ovirt-node-ng-image-update.noarch 0:4.2.4-1.el7 will be >> obsoleting >> ---> Package ovirt-node-ng-image-update-placeholder.noarch >> 0:4.2.3.1-1.el7 will be obsoleted >> --> Finished Dependency Resolution >> >> Dependencies Resolved >> >> ============================================================ >> ============================================================= >> Package Arch >> Version Repository Size >> ============================================================ >> ============================================================= >> Installing: >> ovirt-node-ng-image-update noarch >> 4.2.4-1.el7 ovirt-4.2 647 M >> replacing ovirt-node-ng-image-update-placeholder.noarch >> 4.2.3.1-1.el7 >> >> Transaction Summary >> ============================================================ >> ============================================================= >> Install 1 Package >> >> Total download size: 647 M >> Is this ok [y/d/N]: y >> Downloading packages: >> warning: /var/cache/yum/x86_64/7/ovirt-4.2/packages/ovirt-node-ng-ima >> ge-update-4.2.4-1.el7.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID >> fe590cb7: NOKEY >> Public key for ovirt-node-ng-image-update-4.2.4-1.el7.noarch.rpm is not >> installed >> ovirt-node-ng-image-update-4.2.4-1.el7.noarch.rpm | 647 MB 00:02:07 >> Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 >> Importing GPG key 0xFE590CB7: >> Userid : "oVirt <infra(a)ovirt.org&gt;&quot; >> Fingerprint: 31a5 d783 7fad 7cb2 86cd 3469 ab8c 4f9d fe59 0cb7 >> Package : ovirt-release42-4.2.3.1-1.el7.noarch (installed) >> From : /etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 >> Is this ok [y/N]: y >> Running transaction check >> Running transaction test >> Transaction test succeeded >> Running transaction >> Installing : ovirt-node-ng-image-update-4.2.4-1.el7.noarch 1/3 >> warning: %post(ovirt-node-ng-image-update-4.2.4-1.el7.noarch) scriptlet >> failed, exit status 1 >> Non-fatal POSTIN scriptlet failure in rpm package >> ovirt-node-ng-image-update-4.2.4-1.el7.noarch >> Erasing : ovirt-node-ng-image-update-placeholder-4.2.3.1-1.el7.noarch >> 2/3 >> Cleanup : ovirt-node-ng-image-update-4.2.3.1-1.el7.noarch 3/3 >> warning: file /usr/share/ovirt-node-ng/image >> /ovirt-node-ng-4.2.0-0.20180530.0.el7.squashfs.img: remove failed: No >> such file or directory >> Uploading Package Profile >> Unable to upload Package Profile >> Verifying : ovirt-node-ng-image-update-4.2.4-1.el7.noarch 1/3 >> Verifying : ovirt-node-ng-image-update-4.2.3.1-1.el7.noarch 2/3 >> Verifying : ovirt-node-ng-image-update-placeholder-4.2.3.1-1.el7.noarch >> 3/3 >> >> Installed: >> ovirt-node-ng-image-update.noarch 0:4.2.4-1.el7 >> >> Replaced: >> ovirt-node-ng-image-update-placeholder.noarch 0:4.2.3.1-1.el7 >> >> Complete! >> Uploading Enabled Repositories Report >> Loaded plugins: fastestmirror, product-id, subscription-manager >> This system is not registered with an entitlement server. You can use >> subscription-manager to register. >> Cannot upload enabled repos report, is this client registered? >> >> >> My engine shows the nodes as having no updates, however the major >> components including the kernel version and port 9090 admin GUI show 4.2.3 >> >> Is there anything I can provide to help diagnose the issue? >> >> >> [root@node6-g8-h4 ~]# rpm -qa | grep ovirt >> >> ovirt-imageio-common-1.3.1.2-0.el7.centos.noarch >> ovirt-host-deploy-1.7.3-1.el7.centos.noarch >> ovirt-vmconsole-host-1.0.5-4.el7.centos.noarch >> ovirt-provider-ovn-driver-1.2.10-1.el7.centos.noarch >> ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch >> ovirt-setup-lib-1.1.4-1.el7.centos.noarch >> ovirt-release42-4.2.3.1-1.el7.noarch >> ovirt-imageio-daemon-1.3.1.2-0.el7.centos.noarch >> ovirt-hosted-engine-setup-2.2.20-1.el7.centos.noarch >> ovirt-host-dependencies-4.2.2-2.el7.centos.x86_64 >> ovirt-hosted-engine-ha-2.2.11-1.el7.centos.noarch >> ovirt-host-4.2.2-2.el7.centos.x86_64 >> ovirt-node-ng-image-update-4.2.4-1.el7.noarch >> ovirt-vmconsole-1.0.5-4.el7.centos.noarch >> ovirt-release-host-node-4.2.3.1-1.el7.noarch >> cockpit-ovirt-dashboard-0.11.24-1.el7.centos.noarch >> ovirt-node-ng-nodectl-4.2.0-0.20180524.0.el7.noarch >> python-ovirt-engine-sdk4-4.2.6-2.el7.centos.x86_64 >> >> [root@node6-g8-h4 ~]# yum update >> Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, >> package_upload, product-id, search-disabled-repos, subscription-manager >> This system is not registered with an entitlement server. You can use >> subscription-manager to register. >> Loading mirror speeds from cached hostfile >> * ovirt-4.2-epel: linux.mirrors.es.net >> No packages marked for update >> Uploading Enabled Repositories Report >> Loaded plugins: fastestmirror, product-id, subscription-manager >> This system is not registered with an entitlement server. You can use >> subscription-manager to register. >> Cannot upload enabled repos report, is this client registered? >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/communit >> y/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archiv >> es/list/users(a)ovirt.org/message/UHQMGULUHL4GBBHUBNGOAICJEM6W3RVW/ >> >> >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/communit >> y/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archiv >> es/list/users(a)ovirt.org/message/RTOXFNAXQ3NJBWX7RXOYK5H5RZBHX2OK/ >> >> > > > -- > SANDRO BONAZZOLA > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://red.ht/sig> > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/ message/ACKMTWOUNXB7NWOCRZIOWJI7U5HIQAUV/