Bug #36928
closedRegistering host through load balancer causes REX not to know what smart proxy to choose for 'registered_through'
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2240956
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.
Updated by The Foreman Bot about 1 year ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/10804 added
Updated by Quinn James 12 months ago
- Subject changed from Registering host through load balancer sets content source to 'null' to Registering host through load balancer sets content source to 'null'
- Category set to Hosts
- Target version set to Katello 4.12.0
- Triaged changed from No to Yes
Updated by Jeremy Lenz 12 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|27e9e688851d43c0b1ff6da31ca967df771da986.
Updated by Jeremy Lenz 12 months ago
- Subject changed from Registering host through load balancer sets content source to 'null' to Registering host through load balancer causes REX not to know what capsule to choose for 'registered_through'
Updated by Ian Ballou 11 months ago
- Target version changed from Katello 4.12.0 to Katello 4.11.0
Updated by Ian Ballou 11 months ago
- Subject changed from Registering host through load balancer causes REX not to know what capsule to choose for 'registered_through' to Registering host through load balancer causes REX not to know what smart proxy to choose for 'registered_through'
Updated by Ian Ballou 11 months ago
- Fixed in Releases Katello 4.11.0 added
- Fixed in Releases deleted (
Katello 4.12.0)
Updated by The Foreman Bot 9 months ago
- Pull request https://github.com/Katello/katello/pull/10920 added