Created attachment 1162391 [details] /var/log in ovirt-node Description of problem: Upgrade from ovirt-node ngn 3.6.6/3.6.5 to 3.6.7 failed via "yum install *update*.rpm" Version-Release number of selected component (if applicable): ovirt-node-ng-installer-ovirt-3.6-2016052300.iso imgbased-0.6-0.201605111421git8828a69.el7.centos.noarch ovirt-node-ng-image-update-placeholder-3.6.6-0.3.rc2.el7.noarch ovirt-release-host-node-3.6.6-0.3.rc2.el7.noarch ovirt-release36-snapshot-3.6.6-0.3.rc2.noarch centos-release-7-2.1511.el7.centos.2.10.x86_64 upgrade to: ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch.rpm ovirt-node-ng-installer-ovirt-3.6-2016052700 How reproducible: 100% Steps to Reproduce: 1. Install node ng 4.0(ovirt-3.6 branch) 2. Login host, download latest build update rpm to host: ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch.rpm 3. Upgrade host: # yum install ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch.rpm Actual results: 1. After step3, failed to upgrade to latest build: [root@dhcp-10-125 home]# yum install ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch.rpm Loaded plugins: fastestmirror, imgbased-warning Warning: yum operations are not persisted across upgrades! Examining ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch.rpm: ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch Marking ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package ovirt-node-ng-image-update.noarch 0:3.6.7-0.0.rc1.el7 will be installed --> Processing Dependency: ovirt-node-ng-image = 3.6.7-0.0.rc1.el7 for package: ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch ovirt-node-ng-ovirt-3.6 | 2.9 kB 00:00 Loading mirror speeds from cached hostfile --> Running transaction check ---> Package ovirt-node-ng-image.noarch 0:3.6.7-0.0.rc1.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: ovirt-node-ng-image-update noarch 3.6.7-0.0.rc1.el7 /ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch 0.0 Installing for dependencies: ovirt-node-ng-image noarch 3.6.7-0.0.rc1.el7 ovirt-node-ng-ovirt-3.6 503 M Transaction Summary ================================================================================ Install 1 Package (+1 Dependent package) Total download size: 503 M Installed size: 502 M Is this ok [y/d/N]: y Downloading packages: ovirt-node-ng-image-3.6.7-0.0.rc1.el7.noarch.rpm | 503 MB 06:10 Running transaction check ERROR with transaction check vs depsolve: ovirt-node-ng-image = %{epoch}:3.6.7-0.0.rc1.el7 is needed by ovirt-node-ng-image-update-3.6.7-0.0.rc1.el7.noarch You could try running: rpm -Va --nofiles --nodigest Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx.2016-05-26.08-43.s5GpM_.yumtx Expected results: 1. After step3, should upgrade successful Additional info: Upgrade from ovirt-node-ng-installer-ovirt-3.6-2016041900.iso to latest build(ovirt-node-ng-installer-ovirt-3.6-2016052700) also failed.
Created attachment 1162393 [details] /tmp log in ovirt-node
Yes. There are two rpms: ovirt-node-ng-image-update and ovirt-node-ng-image. The first requires the second. You only downloaded the first. Thus it's normal that it fails. Did you try to just run "yum update" without downloading any rpm?
Dropping testBlocker, because you just need to download two rpms.
(In reply to Fabian Deutsch from comment #2) > Yes. There are two rpms: > ovirt-node-ng-image-update and ovirt-node-ng-image. > The first requires the second. > You only downloaded the first. Thus it's normal that it fails. > > Did you try to just run "yum update" without downloading any rpm? Yes, I tried run "yum update", also failed. And I tested in the build ovirt-node-ng-image-update-3.6.5-1.20160426.0.el7.noarch.rpm before, it is successful in the same way to update
With the new build structure this should now be fixed. Within a branch (-pre, -snapshot, 4.0) yuo should be able to do an update with an rpm, if it has a higher nvr.
Tested version: ovirt-node-ng-installer-ovirt-4.0-snapshot-2016062108.iso ovirt-node-ng-image-update-placeholder-4.0.0-5.201606200219.el7.noarch imgbased-0.7.0-0.201606170910git3cb1db2.el7.centos.noarch The latest update rpm is "ovirt-node-ng-image-update-4.0.0-5.201606200219.el7.noarch.rpm" which is same as tested version, there is no newer update build. So I will test this issue after there is newer update rpm and imgbased.
There is no new build boot entry although it shows upgrade successful with ovirt-node-ng-image-update-4.0.0-5.201606240219.el7.noarch.rpm Test version: 1. Before upgrade: ovirt-node-ng-installer-ovirt-4.0-2016062004.iso imgbased-0.7.0-0.201606081307gitfb92e93.el7.centos.noarch ovirt-node-ng-image-update-placeholder-4.0.0-1.el7.noarch kernel-3.10.0-327.18.2.el7.x86_64 2. After upgrade: imgbased-0.7.0-0.201606081307gitfb92e93.el7.centos.noarch ovirt-node-ng-image-4.0.0-5.201606240219.el7.noarch ovirt-node-ng-image-update-4.0.0-5.201606240219.el7.noarch kernel-3.10.0-327.18.2.el7.x86_64 Test steps: 1. Install ovirt-node-ng-installer-ovirt-4.0-2016062004 via kickstart 2. Login host, download latest build update rpm to host: ovirt-node-ng-image-update-4.0.0-5.201606240219.el7.noarch.rpm 3. Enable repos: CentOS-Base.repo CentOS-Debuginfo.repo cockpit-preview-epel-7.repo ovirt-4.0-pre-dependencies.repo ovirt-4.0-pre.repo 4. check the imgbase layout and packages: # imgbase layout # rpm -qa | grep ovirt-node # rpm -qa | grep kernel 5. Upgrade host: # yum install ovirt-node-ng-image-update-4.0.0-5.201606240219.el7.noarch.rpm 6. Reboot and login host, focus on boot entry and check packages: # imgbase layout # rpm -qa | grep ovirt-node # rpm -qa | grep kernel Actual results: 1. After step4, [root@dhcp-10-16 home]# imgbase layout ovirt-node-ng-4.0.0-0.20160620.0 +- ovirt-node-ng-4.0.0-0.20160620.0+1 [root@dhcp-10-16 home]# rpm -qa | grep ovirt-node ovirt-node-ng-image-update-placeholder-4.0.0-1.el7.noarch [root@dhcp-10-16 home]# rpm -qa | grep kernel kernel-3.10.0-327.18.2.el7.x86_64 2. After step6, There is no new build boot entry, so can not enter new build. [root@dhcp-10-16 yum.repos.d]# imgbase layout ovirt-node-ng-4.0.0-0.20160620.0 +- ovirt-node-ng-4.0.0-0.20160620.0+1 [root@dhcp-10-16 yum.repos.d]# rpm -qa | grep ovirt-node ovirt-node-ng-image-4.0.0-5.201606240219.el7.noarch ovirt-node-ng-image-update-4.0.0-5.201606240219.el7.noarch [root@dhcp-10-16 yum.repos.d]# rpm -qa | grep kernel kernel-3.10.0-327.18.2.el7.x86_64 Expected results: 1. After step6, There should be both new and old build boot entry, can boot with both build. imgbase layout should have both new and old layout. Packages should be newer. Additional info: kickstart file: # cat huzhao.ks liveimg --url=http://10.66.10.22:8090/rhevh/ngn/ovirt-node-ng-installer-ovirt-4.0-2016062004.iso/ovirt-node-ng-image.squashfs.img clearpart --all autopart --type=thinp rootpw --plaintext redhat timezone --utc Asia/Harbin zerombr selinux --enforcing text reboot %post --erroronfail imgbase layout --init imgbase --experimental volume --create /var 4G %end So this bug is not fully fixed, I will change the status to ASSIGNED.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Created attachment 1177127 [details] The displayed info during yum install *update*.rpm
Created attachment 1177128 [details] All logs
I'm not able to reproduce this. You must install ovirt-node-ng-image-update *and* ovirt-node-ng-image. yum should fail if you don't use both (since ovirt-node-ng-image is a dependency of ovirt-node-ng-image-update), but I'll point it out anyway, since your test steps only show -image-update Test version: ovirt-node-ng-installer-4.0-snapshot-2016062704.iso Used packages: ovirt-node-ng-image-4.0.0-5.201607060219.el7.noarch.rpm ovirt-node-ng-image-update-4.0.0-5.201607060219.el7.noarch.rpm yum -y install ovirt-node-ng*.rpm Result: Success imgbase w shows the new layer It's present in the bootloader Can reboot into either version There does appear to be another bug, where newly installed layers take the current date (20160707) rather than the date present in the image. Can you please retest with the given images? Or, failing that, using a snapshot build along with the ovirt-4.0 release should work: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-fc22-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/ http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-fc22-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/
Disregard -- there's no bug with the naming. The RPMs from Jenkins simply have recent squashfs images. This works as expected with an older image RPM. The cause of the "bug" I encountered: # rpm -qlp ovirt-node-ng-image-4.0.0-5.201606240219.el7.noarch.rpm /usr/share/ovirt-node-ng/image /usr/share/ovirt-node-ng/image/ovirt-node-ng-4.0.0-0.20160707.0.el7.squashfs.img /usr/share/ovirt-node-ng/image/product.img
I installed ovirt-node-ng-installer-ovirt-4.0-snapshot-2016071004.iso according to Comment 3, but there is no newer img or *update*.rpm for upgrade now, so I will verify this bug after there is newer img and can upgrade via "yum install *update*.rpm"
Update Comment 13, it should be "according to comment 11"
Test version: 1.Before update: redhat-virtualization-host-4.0-20160714.3 imgbased-0.7.2-0.1.el7ev.noarch redhat-release-virtualization-host-4.0-0.20.el7.x86_64 kernel-3.10.0-327.22.2.el7.x86_64 2. After update: redhat-virtualization-host-4.0-20160714.5 imgbased-0.7.2-0.1.el7ev.noarch redhat-release-virtualization-host-4.0-0.20.el7.x86_64 kernel-3.10.0-327.22.2.el7.x86_64 redhat-virtualization-host-image-update-4.0-20160714.5.el7.noarch Test steps: 1. Install redhat-virtualization-host-4.0-20160714.3 2. Login host, download latest build update rpm to host: redhat-virtualization-host-image-update-4.0-20160714.5.el7.noarch.rpm 3. Configure repos 4. Upgrade host: # yum install redhat-virtualization-host-image-update-4.0-20160714.5.el7.noarch.rpm 5. Reboot and login host #imgbase layout Test results: 1. After step4, update successful 2. After step5, # imgbase layout rhvh-4.0-0.20160714.3 +- rhvh-4.0-0.20160714.3+1 rhvh-4.0-0.20160714.5 +- rhvh-4.0-0.20160714.5+1 So this bug is fixed on redhat-virtualization-host-4.0-20160714.3, during update, there is some error info, BUG 1351942 will trace this issue. So I will change the status to VERIFIED.
Since the problem described in this bug report should be resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a resolution of CURRENT RELEASE. For information on the release, and how to update to this release, follow the link below. If the solution does not work for you, open a new bug report. http://www.ovirt.org/release/4.0.1/