Feature #7745
closed
- Tracker changed from Bug to Feature
- Subject changed from Access rhsm through a ReverseProxy on Capsules to Client systems should be able to route all RHSM traffic through a Capsule.
- Translation missing: en.field_release set to 14
- Triaged changed from No to Yes
- Blocks Tracker #8172: Isolate Client Communication through a Capsule added
test scenario
1) install katello like normal
2) generate certs for capsule and copy to capsule like normal
3) using the capsule installer,
bin/capsule-installer --parent-fqdn "kdev.usersys.redhat.com"\
--register-in-foreman "true"\
--foreman-oauth-key "xxxx"\
--foreman-oauth-secret "xxx"\
--pulp-oauth-secret "xx"\
--certs-tar "~/mycerts.tar"\
--puppet "true"\
--puppetca "true"\
—pulp "true" --parent-reverse-proxy "true" --parent-reverse-proxy-port 8443
4) on a new host, rpm -Uvh http://katello/pub/katello-ca-consumer-latest.noarch.rpm
5) update your /etc/rhsm/rhsm.conf
on a separate host with subscription-manager,
[server]
hostname = capsule-hostname
prefix = /rhsm
port = 8443
6) subscription-manager register --organization Default_Organization
- Translation missing: en.field_release changed from 14 to 23
- Status changed from New to Ready For Testing
- Target version set to 63
- Pull request https://github.com/Katello/katello/pull/4949 added
- Pull request deleted (
)
- Target version changed from 63 to 66
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF