Bug 2024269
| Summary: | Attempt of upgrading Satellite server to 6.7 or 6.8 stops with message "Please run 'foreman-maintain prep-6.10-upgrade' prior to upgrading." when using latest rubygem-foreman_maintain package | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Shekhar Raut <sraut> | |
| Component: | Satellite Maintain | Assignee: | Amit Upadhye <aupadhye> | |
| Status: | CLOSED ERRATA | QA Contact: | sganar | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 6.8.0 | CC: | ahumbe, apatel, aupadhye, gtalreja, jsherril, kgaikwad, mkalyat, mmccune, pcreech, pmendezh, saydas, sganar | |
| Target Milestone: | 6.11.0 | Keywords: | PrioBumpGSS, Triaged | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2027353 (view as bug list) | Environment: | ||
| Last Closed: | 2022-07-05 14:30:00 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
|
Description
Shekhar Raut
2021-11-17 17:58:41 UTC
NOTE: The last working version is 0.7.14-1.el7sat . Any version of foreman-maintain beyond that i.e. 0.8.X is affected by this problem. So downgrading to rubygem-foreman_maintain-0.7.14-1.el7sat.noarch and then using --disable-self-upgrade is the current choice we have. The solution article has been modified to provide the same information. Created redmine issue https://projects.theforeman.org/issues/34039 from this bug Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34039 has been resolved. WORKAROUND: The check is likely failing on the ownership of /var/lib/pulp which may be apache:apache, you can check via: # ls -ld /var/lib/pulp drwxr-xr-x. 9 apache apache 181 Sep 11 2020 /var/lib/pulp If this is the case, run: # chown apache:pulp /var/lib/pulp and re-try the upgrade @ Will there be a fix for this https://bugzilla.redhat.com/show_bug.cgi?id=2024269#c9 ? (In reply to sganar from comment #11) > Will there be a fix for this > https://bugzilla.redhat.com/show_bug.cgi?id=2024269#c9 ? Hey Shubham, The scenario in comment 9 is very unique and will only happen if the external LDAP source has some groups with the same GID as some internal groups of satellite i.e. pulp. But to be honest there is no way to deal with this apart from A) Either change the GID of those LDAP groups in External Source B) Or, We change /etc/nsswitch.conf in satellite to exclude the External Auth-Source from it for User\Group lookup. I had mentioned about it just to ensure that we are aware of different scenarios that can lead to this problem, but this should or perhaps cannot be included in QE testing\verification. So I guess, The only proper way to test it would be to leave the ownership of /var/lib/pulp to apache:apache and then see, if we try to upgrade the Satellite 6 to any version below 6.10, whether it still prompts for that "Please run 'foreman-maintain prep-6.10-upgrade' prior to upgrading" message or not. It should only be prompted during Sat 6.9 -> 6.10 upgrade and if the "foreman-maintain prep-6.10-upgrade" command was not executed for any reason causing the actual group_ownership conflict. Verified. Tested on Satellite 6.9.8 Snap 1.0 rubygem-foreman_maintain-0.8.22 Steps followed: 1. Setup the repositories required for Satellite 6.10 upgrade 2. Run "satellite-maintain upgrade check --target-version" 6.10 / "satellite-maintain upgrade run --target-version 6.10" Observation: satellite-maintain command proceeds for the upgrade as expected. A check is added to check the pulp content's group ownership for 6.9 to 6.10 upgrade. 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 (Moderate: Satellite 6.11 Release), 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-2022:5498 |