Description of problem:
Currently, when we register a Content Host to Satellite, the Host created gets the Satellite server to be the smart_proxy, even if the Host is registered to a Capsule.
When no subnet is defined, the default, and only, remote execution runner should be the content-source Capsule for this host.
This is related to https://bugzilla.redhat.com/show_bug.cgi?id=1508153, more precisely this is the 2nd scenario in https://bugzilla.redhat.com/show_bug.cgi?id=1508153#c8
This should read: The default, and only, remote execution runner MUST be the content-source Capsule for this host, because of network firewalls blocking ssh traffic from other capsules to the host.
I'm changing the component to registration, as the goal is for the registered host, to have set the capsule that was used for registration as "content source", which will lead automatically for REX to use it for it's purposes as well.
Upstream PR: https://github.com/Katello/katello-client-bootstrap/pull/254
Moving this BZ over to the bootstrap component
Verified in Satellite 6.4 Snap 22
Setup a hostgroup that has its content source set to the satellite.
Setup all other prerequisites to use bootstrap.py
Ran bootstra.py on the client, adding in the new argument (--force-content-source), and specifying the capsule
Ran a rex job against the host
The content source was successfully set to the capsule
The remote execution was completed by the capsule
Full bootstrap command:
python bootstrap.py -l admin -s <capsule> -o "Default Organization" -L "Default Location" -g nouse -a rhel7 --rex --force-content-source --force --add-domain
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.