Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2048986 - "foreman-maintain health check --label validate-yum-config" command failed with message "clean_requirements_on_remove=True Unset this configuration as it is risky while yum update or upgrade!"
Summary: "foreman-maintain health check --label validate-yum-config" command failed wi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: sganar
URL:
Whiteboard:
Depends On:
Blocks: 1693733
TreeView+ depends on / blocked
 
Reported: 2022-02-01 09:45 UTC by sganar
Modified: 2022-07-19 10:50 UTC (History)
9 users (show)

Fixed In Version: rubygem-foreman_maintain-1.0.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:32:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34761 0 Normal Closed "foreman-maintain health check --label validate-yum-config" command failed with message "clean_requirements_on_remove=Tr... 2022-04-14 12:24:52 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:33:00 UTC

Description sganar 2022-02-01 09:45:28 UTC 
Description of problem:
"foreman-maintain health check --label validate-yum-config" fails with the message

"clean_requirements_on_remove is set in /etc/yum.conf as below: 
clean_requirements_on_remove=True 
Unset this configuration as it is risky while yum update or upgrade!"

Version-Release number of selected component (if applicable):
Satellite 7.0 Rhel 8.5

How reproducible:
Always

Steps to Reproduce:
1. Have a fresh Satellite on RHEL 8.5
2. Run foreman-maintain health check --label validate-yum-config

Actual results:
Check fails

Expected results:
Check should pass

Additional info:
Comment 8 Amit Upadhye 2022-04-12 13:33:12 UTC 
Created redmine issue https://projects.theforeman.org/issues/34761 from this bug
Comment 9 Bryan Kearney 2022-04-14 12:04:45 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34761 has been resolved.
Comment 10 sganar 2022-05-23 10:51:04 UTC 
Verified.

Tested on Satellite 6.11.0 Snap 21.0

Steps followed: 
1. Have a fresh Satellite on RHEL 8
2. Run foreman-maintain health check --label validate-yum-config

Observation: 
Check passes
```# foreman-maintain health check --label validate-yum-config
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check to validate yum configuration before upgrade:                   [OK]
--------------------------------------------------------------------------------```
Comment 13 errata-xmlrpc 2022-07-05 14:32:43 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.