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:
In capsule-certs-generate output, the scenario used is "foreman-proxy-content" instead of "capsule". There are also upstream references to smart proxies in the instructions
i.e.
[root@sat63qedev ~]# !251
capsule-certs-generate --certs-tar ~/capsule-63-qa.john.example.com.tar --foreman-proxy-fqdn capsule-63-qa.john.example.com
Installing Done [100%] [.............................................................................................]
Success!
To finish the installation, follow these steps:
If you do not have the smartproxy registered to the Katello instance, then please do the following:
1. yum -y localinstall http://sat63qedev.example.com/pub/katello-ca-consumer-latest.noarch.rpm
2. subscription-manager register --org "Default_Organization"
Once this is completed run the steps below to start the smartproxy installation:
1. Ensure that the foreman-installer-katello package is installed on the system.
2. Copy the following file /root/capsule-63-qa.john.example.com.tar to the system capsule-63-qa.john.example.com at the following location /root/capsule-63-qa.john.example.com.tar
scp /root/capsule-63-qa.john.example.com.tar root.example.com:/root/capsule-63-qa.john.example.com.tar
3. Run the following commands on the Foreman proxy (possibly with the customized
parameters, see satellite-installer --scenario foreman-proxy-content --help and
documentation for more info on setting up additional services):
satellite-installer --scenario foreman-proxy-content\
--foreman-proxy-content-parent-fqdn "sat63qedev.example.com"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-foreman-base-url "https://sat63qedev.example.com"\
--foreman-proxy-trusted-hosts "sat63qedev.example.com"\
--foreman-proxy-trusted-hosts "capsule-63-qa.john.example.com"\
--foreman-proxy-oauth-consumer-key "KkA4g5VnYUvsP7ne3aafkcByR6QRWDAo"\
--foreman-proxy-oauth-consumer-secret "NVFfCnSUWkHBqAxBV7bdfXX7pJqCThZn"\
--foreman-proxy-content-pulp-oauth-secret "VnkNXxRh4mPc24RpGjxmpseSEw6zTbcz"\
--foreman-proxy-content-certs-tar "/root/capsule-63-qa.john.example.com.tar"\
--puppet-server-foreman-url "https://sat63qedev.example.com"
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.Run (on Satellite) capsule-certs-generate --certs-tar ~/HOSTNAME.tar --foreman-proxy-fqdn HOSTNAME
2.Try to follow instructions and observe scenario not found errors
3.
Actual results:
foreman-proxy-content scenario is used in the installer and references are made to smart proxies, not capsules
Expected results:
Capsule installer is used and references are made to capsules
Additional info: