Bug 1502920
| Summary: | File missing after upgrade of RHVH node from version RHVH-4.1-20170925.0 to latest. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ulhas Surse <usurse> | |
| Component: | ovirt-node-ng | Assignee: | Ryan Barry <rbarry> | |
| Status: | CLOSED ERRATA | QA Contact: | Huijuan Zhao <huzhao> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.1.6 | CC: | arusso, bgraveno, cshao, dfediuck, huzhao, qiyuan, rbarry, sbonazzo, sigbjorn, sraje, usurse, yaniwang, ycui, yzhao | |
| Target Milestone: | ovirt-4.2.0 | Keywords: | ZStream | |
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
|
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | imgbased-1.0.3 | Doc Type: | Bug Fix | |
| Doc Text: |
This update ensures that Red Hat Virtualization Host (RHVH) synchronizes system-specific data in /usr. This ensures that systems registered to Satellite are still able to receive updates after upgrading.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1506550 (view as bug list) | Environment: | ||
| Last Closed: | 2018-05-15 17:57:44 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: | 1506550 | |||
|
Description
Ulhas Surse
2017-10-17 04:03:53 UTC
This will also be true for any other volatile data stored in /usr We made a strong effort in RHV to move all volatile data to /var, as /usr on RHVH is per-image. For the rpmdb, we've done the reverse by symlinking /var/lib/rpm to /usr/share/rpm We can easily do this for /usr/share/rhn. Does Satellite keep any other volatile data in /usr? F(In reply to Ryan Barry from comment #2) > This will also be true for any other volatile data stored in /usr > > We made a strong effort in RHV to move all volatile data to /var, as /usr on > RHVH is per-image. > > For the rpmdb, we've done the reverse by symlinking /var/lib/rpm to > /usr/share/rpm > > We can easily do this for /usr/share/rhn. Does Satellite keep any other > volatile data in /usr? For the satellite to communicate with the client, these following three files should be available with the configuration intact. ~~~ /etc/sysconfig/rhn/up2date /etc/sysconfig/rhn/systemid /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT ~~~ So, here the concern is only with the certificate file which is missing after the upgrade. Others are available with the configuration. The similar issue found with "/etc/resolv.conf" file. The changes made in 'resolv.conf' with image 'rhvh-4.1-0.20170925.0' missing after update to newer image 'rhvh-4.1-0.20171002.0'. Steps to reproduce : 1) Build RHV-H host using RHVH-4.1-20170925.0-RHVH-x86_64-dvd1.iso 2) Join to RHEV-M DC and cluster 3) Make changes to "/etc/resolv.conf" 3) Put newly build host into maintenance mode 4) In RHEV-M webUI, check for upgrades 5) In RHEV-M webUI, upgrade newly built host 6) After newly built host has rebooted, check /etc/resolv.conf, note the modified settings line is missing. QE can reproduce this issue, but not exactly according to the customer's steps due to no suitable satellite server. 1. For the file "/etc/resolv.conf"(configuration file for DNS resolvers), if modify this file directly, the modification will missing when restart network service, so this issue is not related to upgrade, as the method of modify the file is not suitable. 1.1 I tried to modify /etc/sysconfig/network-scripts/ifcfg-$NIC(such as add: DNS1=10.72.17.6), 1.2 Run "#service network restart", then "/etc/resolv.conf" is modified automately(add: nameserver 10.72.17.6) 1.3 Upgrade rhvh from rhvh-4.1-0.20170925.0 to rhvh-4.1-0.20171002.0 , the changes made in 'resolv.conf' in step 1.2 are persisted. 2. For the file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT, it is not exit after upgrade. Test version: # imgbase layout rhvh-4.1-0.20170925.0 +- rhvh-4.1-0.20170925.0+1 rhvh-4.1-0.20171002.0 +- rhvh-4.1-0.20171002.0+1 Test steps: 2.1 Install rhvh-4.1-0.20170925.0 2.2 Touch new file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT 2.3 Upgrade rhvh from rhvh-4.1-0.20170925.0 to rhvh-4.1-0.20171002.0 2.4 Check file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Actual results: After step 2.4, there is no file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT. Expected results: After step 2.4, there should be file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT. Test version: # imgbase layout rhvh-4.1-0.20171205.0 +- rhvh-4.1-0.20171205.0+1 rhvh-4.2.0.5-0.20171207.0 +- rhvh-4.2.0.5-0.20171207.0+1 Test steps: 1 Install rhvh-4.1-0.20171205.0 2 Touch new file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT 3 Upgrade rhvh from rhvh-4.1-0.20171205.0 to rhvh-4.2.0.5-0.20171207.0 4 Check file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Actual results: After step 4, there is file /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT. So this issue is fixed in rhvh-4.2.0.5-0.20171207.0, change the status to verified. According to comment 13, change the status to VERIFIED. 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:1524 BZ<2>Jira Resync sync2jira sync2jira |