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:
capsule-certs-generate shows "foreman-installer --scenario foreman-proxy-content"
Version-Release number of selected component (if applicable):
satellite-installer-6.6.0.11-1.beta.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. # capsule-certs-generate --foreman-proxy-fqdn caps1.longscale.local --certs-tar /tmp/aaa.tar
Actual results:
[root@satellite ~]# capsule-certs-generate --foreman-proxy-fqdn caps1.longscale.local --certs-tar /tmp/aaa.tar
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://satellite.longscale.local/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 /tmp/aaa.tar to the system caps1.longscale.local at the following location /root/aaa.tar
scp /tmp/aaa.tar root.local:/root/aaa.tar
3. Run the following commands on the Foreman proxy (possibly with the customized
parameters, see foreman-installer --scenario foreman-proxy-content --help and
documentation for more info on setting up additional services):
foreman-installer --scenario foreman-proxy-content\
--certs-tar-file "/root/aaa.tar"\
--foreman-proxy-content-parent-fqdn "satellite.longscale.local"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-foreman-base-url "https://satellite.longscale.local"\
--foreman-proxy-trusted-hosts "satellite.longscale.local"\
--foreman-proxy-trusted-hosts "caps1.longscale.local"\
--foreman-proxy-oauth-consumer-key "MtJ2ptijK6tXf26bZALDUyzJWa97UzcB"\
--foreman-proxy-oauth-consumer-secret "Ey2uEfvdmeo3axP7U4iQrDhUfRawAuu6"\
--puppet-server-foreman-url "https://satellite.longscale.local"
And it does not work:
[root@caps1 ~]# foreman-installer --scenario foreman-proxy-content
ERROR: Selected scenario is DISABLED, can not continue.
Use --list-scenarios to list available options.
You can also --enable-scenario SCENARIO to make the selected scenario available.
[root@caps1 ~]# foreman-installer --list-scenarios
Available scenarios
Capsule (use: --scenario capsule)
Install a stand-alone Satellite Capsule.
Satellite (use: --scenario satellite)
Install Satellite server
Expected results:
Command should start with:
satellite-installer --scenario capsule ...