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:
From customer case with failing Remote execution that started after upgrade to 6.13. Troubleshooting resulted in finding that host's Content source gets set to null when re-registering. That resulted in Remote execution not working with error message:
Failed to initialize: RuntimeError - Could not use any Capsule for the ["SSH", "Script"] job. Consider configuring remote_execution_global_proxy, remote_execution_fallback_proxy in settings
Due to network segmentation, setting anything other than:
Fallback to Any Capsule: Yes
Enable Global Capsule: No
will fail for them.
Version-Release number of selected component (if applicable):
[root@jb-rhel8-sat613 ~]# rpm -qa | grep satellite
satellite-installer-6.13.0.7-1.el8sat.noarch
satellite-common-6.13.4-1.el8sat.noarch
ansible-collection-redhat-satellite-3.9.0-2.el8sat.noarch
rubygem-foreman_theme_satellite-11.0.0.5-1.el8sat.noarch
satellite-6.13.4-1.el8sat.noarch
ansible-collection-redhat-satellite_operations-1.3.0-2.el8sat.noarch
satellite-maintain-0.0.1-1.el8sat.noarch
satellite-cli-6.13.4-1.el8sat.noarch
How reproducible:
Always
Steps to Reproduce:
Satellite server: jb-rhel8-sat613.jb.lab
Client: jb-rhel8-test01.jb.lab
Capsules: jb-rhel8-sat613-caps01.jb.lab, jb-rhel8-sat613-caps02.jb.lab
Load balancer: jb-haproxy01.jb.lab
1. Setup satellite and capsules with load balancing according to latest documentation.
2. Register or re-register a host with --serverurl=<loadbalancer-address or ip-address for capsule> sets Content source to null.
[root@jb-rhel8-test01 ~]# subscription-manager register --serverurl=https://jb-haproxy01.jb.lab --force
3. Register or re-register a host with --serverurl=<capsule hostname> sets the correct Content source.
[root@jb-rhel8-test01 ~]# subscription-manager register --serverurl=https://jb-rhel8-sat613-caps02.jb.lab --force
Actual results:
[root@jb-rhel8-sat613 ~]# hammer host info --name jb-rhel8-test01.jb.lab | grep -A2 'Content Source'
Content Source:
Id:
Name:
Expected results:
[root@jb-rhel8-sat613 ~]# hammer host info --name jb-rhel8-test01.jb.lab | grep -A2 'Content Source'
Content Source:
Id: 2
Name: jb-rhel8-sat613-caps01.jb.lab
Additional info:
Debug logs attached
When reinstalling katello-ca-consumer-latest.rpm and using registering with no --serverurl, content source is
properly set from value in package.
Verified in 6.15.0 snap 6 using the load balanced setup (Satellite, 2 Capsules, HAproxy)
After registering or re-registering a host to a load balanced capsule (via global registration and `subscription-manager register --serverurl=...`) the host had the Content Source set properly and the REX commands run against the host succeeded.
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.15.0 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-2024:2010