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:
Package foreman-proxy-selinux is available in the repository 'rhel-7-server-satellite-capsule-6.10-rpms'
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Install the package 'foreman-proxy-selinux'
2. Try to restart the selinux
3. Got the error:
~~~
# systemctl restart foreman-proxy
Job for foreman-proxy.service failed because the control process exited with error code. See "systemctl status foreman-proxy.service" and "journalctl -xe" for details.
~~~
Actual results:
The foreman-proxy failed to start
Expected results:
The foreman-proxy started with success
Additional info:
We had the Bugzilla below about this package:
- Don't ship foreman-proxy-selinux in satellite and capsule repos
https://bugzilla.redhat.com/show_bug.cgi?id=1840533
Then, I believe we published the package again but it is not needed:
~~~
# yum list foreman-proxy-selinux
Loaded plugins: enabled_repos_upload, package_upload, product-id, search-disabled-repos, subscription-manager
Installed Packages
foreman-proxy-selinux.noarch 2.5.2-1.el7sat @rhel-7-server-satellite-capsule-6.10-rpms
Uploading Enabled Repositories Report
Loaded plugins: product-id, subscription-manager
~~~
VERIFIED.
@Satellite 6.12.0 Snap11
by following manual steps:
@Capsule
# yum --disableplugin=foreman-protector list foreman-proxy-selinux --showd
...
Error: No matching Packages to list
>>> foreman-proxy-selinux is no longer present in the Capsule repo
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.12 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:8506