Bug 1669498
| Summary: | Upgrade from 6.3 to 6.4, PostgreSQL is removed during the upgrade process. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Rudnei Bertol Jr. <rbertolj> |
| Component: | Satellite Maintain | Assignee: | Kavita <kgaikwad> |
| Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | apatel, egolov, gpadholi, inecas, jpathan, kgaikwad, mbacovsk, vijsingh, wpinheir |
| Target Milestone: | 6.9.0 | Keywords: | Triaged, Upgrades |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_maintain-0.7.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-04-21 14:48:22 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
Rudnei Bertol Jr.
2019-01-25 13:53:15 UTC
I think the foreman-maintain should prevent the upgrade if the option `clean_requirements_on_remove` is set in yum: this is not a tested configuration and there is risk more things like that would happen. Created redmine issue https://projects.theforeman.org/issues/30234 from this bug Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30234 has been resolved. Verified. Version Tested: Satellite-6.9.0 Snap 6 and rubygem-foreman_maintain-0.7.0-1.el7sat.noarch Steps followed: **** set exclude option in /etc/yum.conf **** # foreman-maintain health check --label validate-yum-config Running ForemanMaintain::Scenario::FilteredScenario ================================================================================ Check to validate yum configuration before upgrade: [FAIL] exclude is set in /etc/yum.conf as below: exclude='cat* bear*' Unset this configuration as it is risky while yum update or upgrade! -------------------------------------------------------------------------------- Scenario [ForemanMaintain::Scenario::FilteredScenario] failed. The following steps ended up in failing state: [validate-yum-config] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="validate-yum-config" **** set exclude and clean_requirements_on_remove=1 option in /etc/yum.conf **** # foreman-maintain health check --label validate-yum-config Running ForemanMaintain::Scenario::FilteredScenario ================================================================================ Check to validate yum configuration before upgrade: [FAIL] exclude,clean_requirements_on_remove are set in /etc/yum.conf as below: exclude='cat* bear*' clean_requirements_on_remove=1 Unset this configuration as it is risky while yum update or upgrade! -------------------------------------------------------------------------------- Scenario [ForemanMaintain::Scenario::FilteredScenario] failed. The following steps ended up in failing state: [validate-yum-config] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="validate-yum-config" **** set clean_requirements_on_remove=1 option in /etc/yum.conf **** # foreman-maintain health check --label validate-yum-config Running ForemanMaintain::Scenario::FilteredScenario ================================================================================ Check to validate yum configuration before upgrade: [FAIL] clean_requirements_on_remove is set in /etc/yum.conf as below: clean_requirements_on_remove=1 Unset this configuration as it is risky while yum update or upgrade! -------------------------------------------------------------------------------- Scenario [ForemanMaintain::Scenario::FilteredScenario] failed. The following steps ended up in failing state: [validate-yum-config] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="validate-yum-config" **** set clean_requirements_on_remove=0 option in /etc/yum.conf **** # foreman-maintain health check --label validate-yum-config Running ForemanMaintain::Scenario::FilteredScenario ================================================================================ Check to validate yum configuration before upgrade: [OK] -------------------------------------------------------------------------------- Observation: validate_yum_config check was able to detect exclude set and clean_requirements_on_remove=1 option present in /etc/yum.conf 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 (Satellite 6.9 Satellite Maintenance 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/RHBA-2021:1312 |