Project

General

Profile

Actions

Bug #29617

closed

[RFE] EPEL repository check should be renamed to non-Red Hat repository check

Added by Kavita Gaikwad almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Description of problem:

Satellite maintain upgrade check failing when we have an epel repository enabled on satellite 6.7 Beta

Version-Release number of selected component (if applicable):

satellite-6.7.0-5.beta.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch

How reproducible:
New installation

Steps to Reproduce:
1. Install new Satellite 6.7 beta
2. Try to perform minor update steps with # satellite-maintain upgrade check
3.

Actual -

Running Checks before upgrading to Satellite 6.7.z ================================================================================
Check number of fact names in database: [OK]
--------------------------------------------------------------------------------
Check for verifying syntax for ISP DHCP configurations: [SKIPPED]
DHCP feature is not enabled
--------------------------------------------------------------------------------
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [OK]
--------------------------------------------------------------------------------
Check for paused tasks: [OK]
--------------------------------------------------------------------------------
Check to verify no empty CA cert requests exist: [OK]
--------------------------------------------------------------------------------
Check whether system is self-registered or not: [OK]
--------------------------------------------------------------------------------
Check to make sure root(/) partition has enough space: [OK]
--------------------------------------------------------------------------------
Check to validate candlepin database: [OK]
--------------------------------------------------------------------------------
Check if EPEL repository enabled on system:
\ Checking for presence of EPEL repository [FAIL]
System is subscribed to EPEL repository
--------------------------------------------------------------------------------
Check for running tasks: [OK]
--------------------------------------------------------------------------------
Check for old tasks in paused/stopped state: [OK]
--------------------------------------------------------------------------------
Check for pending tasks which are safe to delete: [OK]
--------------------------------------------------------------------------------
Check for tasks in planning state: [OK]
--------------------------------------------------------------------------------
Check to verify if any hotfix installed on system:
/ Checking for presence of hotfix(es). It may take some time to verify.
[OK]
--------------------------------------------------------------------------------
Check if TMOUT environment variable is set: [OK]
--------------------------------------------------------------------------------
Check if any upstream repositories are enabled on system: | Checking for presence of upstream repositories [OK]
--------------------------------------------------------------------------------
Check if yum exclude list is configured: [OK]
--------------------------------------------------------------------------------
Check for roles that have filters with multiple resources attached: [OK]
--------------------------------------------------------------------------------
Check for recommended disk speed of pulp, mongodb, pgsql dir.: [SKIPPED]
--------------------------------------------------------------------------------
Check whether reports have correct associations: [OK]
--------------------------------------------------------------------------------
Validate availability of repositories:
/ Validating availability of repositories for 6.7 [OK]
--------------------------------------------------------------------------------
Scenario [Checks before upgrading to Satellite 6.7.z] failed.

The following steps ended up in failing state:

[check-epel-repository]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="check-epel-repository"

Expected results:
It seems that this is happening due to we have enabled "ansible-runner" repos on satellite server.

  1. cat /etc/yum.repos.d/ansible-runner.repo
    [ansible-runner]
    name=Ansible runner
    baseurl=https://releases.ansible.com/ansible-runner/rpm/epel-7-$basearch/
    enabled=1
    gpgcheck=True
    gpgkey=https://releases.ansible.com/keys/RPM-GPG-KEY-ansible-release.pub

If this is an expected behavior then we should have added in the documentation that we should use --whitelist="check-epel-repository" parameter in SM

Additional info:

As this bug shows, the upgrade check is properly finding non-Red Hat repositories that are enabled are failing but it is confusing to the user as it said it found an EPEL respository, when in fact, it was ansible.com repositories.
We should rename this check. As a user with the above error, I would not know how to resolve this as there was no EPEL repo enabled.


Related issues 1 (0 open1 closed)

Related to Foreman Maintain - Bug #29002: foreman-maintain should check for epel repo firstClosedKavita GaikwadActions
Actions #1

Updated by Kavita Gaikwad almost 4 years ago

  • Related to Bug #29002: foreman-maintain should check for epel repo first added
Actions #2

Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_maintain/pull/316 added
Actions #3

Updated by Kavita Gaikwad almost 4 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF