Bug 1425502
| Summary: | ovirt-imageio-daemon not running after 3.6 NGN to 4.1 NGN upgrade: /var/log/ovirt-imageio-daemon not created | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-node | Reporter: | Jiri Belka <jbelka> |
| Component: | General | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Huijuan Zhao <huzhao> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1 | CC: | bugs, cshao, danken, derez, jbelka, mgoldboi, mwest, nsoffer, rbarry, sirao, ylavi |
| Target Milestone: | ovirt-4.1.1-1 | Flags: | rule-engine:
ovirt-4.1+
rule-engine: exception+ mgoldboi: planning_ack+ sbonazzo: devel_ack+ ycui: testing_ack+ |
| Target Release: | 4.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | imgbased-0.9.20-0.1.el7ev | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Since /var is a separate volume, imgbased did not previously attempt to merge the contents of /var on the new layer with the contents of the /var filesystem
Consequence: Paths in /var present on the new image may not be present after upgrades.
Fix: imgbased now syncs /var
Result: Files in /var are present after upgrading, and services which depend on those files can start successfully.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-21 09:31:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1421098 | ||
|
Description
Jiri Belka
2017-02-21 15:22:17 UTC
which version of ovirt-imageio-daemon is installed after upgrade? (In reply to Dan Kenigsberg from comment #2) > which version of ovirt-imageio-daemon is installed after upgrade? 3.6 ngn doesn't have imageio at all, so after upgrade to 4.1 ngn it will have its own imageio version: [root@dell-r210ii-03 ~]# rpm -qa ovirt\* ovirt-setup-lib-1.0.1-1.el7ev.noarch ovirt-node-ng-nodectl-4.0.4-0.20160920.0.el7.noarch ovirt-hosted-engine-ha-1.3.5.9-2.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch ovirt-hosted-engine-setup-1.3.7.3-1.el7ev.noarch ovirt-vmconsole-host-1.0.4-1.el7ev.noarch ovirt-host-deploy-1.4.1-1.el7ev.noarch [root@dell-r210ii-03 ~]# rpm -qa \*virtualization-host redhat-release-virtualization-host-3.6-0.2.el7.x86_64 after upgrade to 4.1-beta ngn: [root@dell-r210ii-03 ~]# rpm -qa ovirt\* ovirt-node-ng-nodectl-4.1.0-0.20170104.1.el7.noarch ovirt-imageio-common-1.0.0-0.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-setup-lib-1.1.0-1.el7ev.noarch ovirt-vmconsole-host-1.0.4-1.el7ev.noarch ovirt-imageio-daemon-1.0.0-0.el7ev.noarch ovirt-hosted-engine-ha-2.1.0.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.1.0.1-1.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch ovirt-host-deploy-1.6.0-1.el7ev.noarch [root@dell-r210ii-03 ~]# rpm -qa \*virtualization-host redhat-release-virtualization-host-4.1-0.6.el7.x86_64 and again /var/log/ovirt-imageio-daemon is the issue. I would expect that this is because /var is a separate filesystem. We rsync the new FS over to the LV, then mount /var (which does not have /var/log/ovirt-imageio-daemon) on top of it. We probably need an additional hook inside imgbased's osupdater to copy paths on the new /var which do not exist on the LV. Daniel, is this a dup of bug 1401901 ? shouldn't ovirt-imageio--1.0.0-0.el7ev.noarch have fixed this already? (In reply to Dan Kenigsberg from comment #5) > Daniel, is this a dup of bug 1401901 ? > > shouldn't ovirt-imageio--1.0.0-0.el7ev.noarch have fixed this already? @Nir - what do you think? An issue with /var/log as suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1425502#c4 (In reply to Daniel Erez from comment #6) > @Nir - what do you think? An issue with /var/log as suggested in > https://bugzilla.redhat.com/show_bug.cgi?id=1425502#c4 Yes, seems that comment 4 is correct. Is this patch included in latest build for 4.1? Should this be modified? Test version:
From:
redhat-virtualization-host-3.6-20170404.0
To:
redhat-virtualization-host-4.1-20170403.0
imgbased-0.9.20-0.1.el7ev.noarch
Test steps:
1. Install redhat-virtualization-host-3.6-20170404.0
2. Add it to engine 3.6(3.6 cluster), add NFS storage domain to host in engine UI
3. Login rhvh-3.6, setup local repos, update it to rhvh-4.1 redhat-virtualization-host-4.1-20170403.0
# yum update
4. Reboot and login rhvh-4.1, check ovirt-imageio-daemon status, check rhvh-4.1 status in engine UI
Test results:
After step4, ovirt-imageio-daemon is active, rhvh-4.1 is up in engine UI.
[root@dhcp-10-16 ~]# systemctl status ovirt-imageio-daemon
● ovirt-imageio-daemon.service - oVirt ImageIO Daemon
Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 2017-04-06 01:45:13 EDT; 8min ago
Main PID: 1118 (ovirt-imageio-d)
CGroup: /system.slice/ovirt-imageio-daemon.service
└─1118 /usr/bin/python /usr/bin/ovirt-imageio-daemon
Apr 06 01:45:08 localhost.localdomain systemd[1]: Starting oVirt ImageIO Daemon...
Apr 06 01:45:13 localhost.localdomain systemd[1]: Started oVirt ImageIO Daemon.
So this bug is fixed in imgbased-0.9.20-0.1.el7ev.noarch, change the status to VERIFIED.
|