Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
ansible-runner implementation depends on third party repository ansible-runner package.
Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 12
How reproducible:
- Always
Steps to Reproduce:
I have noticed that each time satellite-installer run it creates ansible-runner.repo
To enable ansible-runner implementation being an default option, we depend on the 'ansible-runner' package
and it's installed from a third party repository.
Original issue(change which introduced this dependency): https://projects.theforeman.org/issues/27264
eg. If I install package using 'foreman-maintain package install' command, this will run satellite-installer and will create ansible-runner repo.
As this repo contains 'epel' keyword in it's baseurl, check-non-redhat-repository check of foreman-maintain will keep on failing. [0]
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1803968
# 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
Actual results:
- epel repo is installed
Expected results:
- no epel repo is intalled
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 (Important: Satellite 6.8 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-2020:4366
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 (Important: Satellite 6.8 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-2020:4366