Bug 1608828
| Summary: | [downstream clone - 4.2.6] Unable to perform upgrade from 4.1 to 4.2 due to selinux related errors. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | ovirt-engine | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.11 | CC: | didi, eheftman, lsurette, lsvaty, michal.skrivanek, mperina, omachace, rabraham, Rhev-m-bugs, srevivo, tburke, ylavi |
| Target Milestone: | ovirt-4.2.6 | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.6 | Doc Type: | Bug Fix |
| Doc Text: |
Under certain conditions an issue with a change in selinux policy, and the script that converts a selinux policy in the old format to the new format of the selinux policy, causes the engine-setup upgrade to postgresql to fail for upgrades from 4.1.to 4.2.
In this release, engine-setup checks for this issue, and aborts the upgrade with a clear error message.
To prevent this, reinstall the rh-postgresql95-runtime package by running 'yum reinstall rh-postgresql95-runtime', then run engine-setup again.
|
Story Points: | --- |
| Clone Of: | 1594615 | Environment: | |
| Last Closed: | 2018-09-04 13:41:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1594615 | ||
| Bug Blocks: | |||
|
Description
RHV bug bot
2018-07-26 11:03:49 UTC
This seems similar to bug 1518253. Can you try if running 'yum reinstall rh-postgresql95-runtime' resolves the issue? (Originally by Ondra Machacek) (In reply to Ondra Machacek from comment #5) > This seems similar to bug 1518253. Can you try if running 'yum reinstall > rh-postgresql95-runtime' resolves the issue? Hi , It worked for me after doing a reinstall of the package again. Ribu (Originally by Ribu Abraham) If it's indeed fully reproducible, might try again to debug this - and open a bug on selinux policy and/or postgresql. At the time, we didn't manage to reproduce, thus made bug 1518253 a known issue. If we fail to reproduce, but still want a workaround, that's an option too. Please see the discussion on bug 1518253 and try to provide as many relevant details as possible, including: What state did you start from? Is this a new system, or upgraded from older ones (seems like < 7.3 seems to be relevant)? Was it rebooted, or not, during an upgrade process? Etc. (Originally by didi) (In reply to Yedidyah Bar David from comment #7) > If it's indeed fully reproducible, might try again to debug this - and open > a bug on selinux policy and/or postgresql. > > At the time, we didn't manage to reproduce, thus made bug 1518253 a known > issue. > > If we fail to reproduce, but still want a workaround, that's an option too. > > Please see the discussion on bug 1518253 and try to provide as many relevant > details as possible, including: > > What state did you start from? Is this a new system, or upgraded from older > ones (seems like < 7.3 seems to be relevant)? > > Was it rebooted, or not, during an upgrade process? > > Etc. Based on the requested information. This is a fresh 4.1 install on RHEL 7.4 . The machine didn't require a reboot as there was no kernel update. The error on first try received for selinux has been attached for your information. (Originally by Ribu Abraham) Ribu, thanks for the update, but this isn't enough - we already have this information in bug 1518253. "Reproducible" means you can provide this: 1. Cleanly install a machine with RHEL 2. ? 3. ? 4. ? 5. Get this error If you can't, I will sadly have to close this as a duplicate. If you can attach a sosreport, it might help too - although, as I said, we already spent quite some time on a real machine demonstrating this behavior but still failed to reproduce. Thanks. (Originally by didi) (In reply to Yedidyah Bar David from comment #10) > Ribu, thanks for the update, but this isn't enough - we already have this > information in bug 1518253. "Reproducible" means you can provide this: > > 1. Cleanly install a machine with RHEL > 2. ? > 3. ? > 4. ? > 5. Get this error > > If you can't, I will sadly have to close this as a duplicate. > > If you can attach a sosreport, it might help too - although, as I said, we > already spent quite some time on a real machine demonstrating this behavior > but still failed to reproduce. Thanks. I have tried to recreate the issue for which it works for me at the moment based on a fresh install of RHEL 7 followed by RHV 4.1 setup and upgrade to 4.2. The issue for Postgres SELinux related errors no longer shows up Ribu (Originally by Ribu Abraham) Decided to "fix" by making engine-setup check this and fail, with a message suggesting a workaround. Still not sure how to reproduce. For how I "reproduced" and verified, see my comment starting with "Verified by:" in gerrit: https://gerrit.ovirt.org/93147 If someone does manage to come up with a real reproducer, not involving zeroing out file_contexts.subs , I suggest to reopen bug 1518599, if you want. (Originally by didi) This can be tested with 4.2 nightly: latest engine published there is currently ovirt-engine-4.2.6.1-0.0.master.20180801123732.git9367424.el7 which includes this fix. ok upgrade to 4.2.6.0-1 without any problem May 30 13:51:11 Installed: ovirt-engine-4.1.11.2-0.1.el7.noarch Aug 14 15:29:11 Installed: ovirt-engine-4.2.6-0.1.el7ev.noarch Didi With regard to the doc text, if this bug is a duplicate, does this mean I can use this part of the doc text from bug 1518253: To prevent this, reinstall the rh-postgresql95-runtime package by running 'yum reinstall rh-postgresql95-runtime', then run engine-setup again. (In reply to Emma Heftman from comment #18) > Didi > With regard to the doc text, if this bug is a duplicate, does this mean I > can use this part of the doc text from bug 1518253: > > To prevent this, reinstall the rh-postgresql95-runtime package by running > 'yum reinstall rh-postgresql95-runtime', then run engine-setup again. Yes. We didn't fix the issue, because we failed to reproduce. The only change here is that the failure will be sooner, and with this message: [ INFO ] Verifying PostgreSQL SELinux file context rules [ ERROR ] SELinux file context rules for PostgreSQL are missing SELinux file context rules for PostgreSQL are missing. For more information, see: https://bugzilla.redhat.com/1518599 . You can try fixing this by running this command: # yum reinstall rh-postgresql95-runtime Then you can try running Setup again. [ ERROR ] Failed to execute stage 'Environment customization': SELinux file context rules for PostgreSQL are missing 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/RHBA-2018:2623 |