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.
Bug 1470679 - capsule-certs-generate gives incorrect instructions
Summary: capsule-certs-generate gives incorrect instructions
Keywords:
Status: CLOSED DUPLICATE of bug 1458749
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Branding
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-13 12:54 UTC by Peter Ondrejka
Modified: 2017-08-08 08:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 08:34:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Peter Ondrejka 2017-07-13 12:54:33 UTC 
Description of problem:

The output of successful capsule-cert-genreate:

]# capsule-certs-generate --node-fqdn mycapsule.example.com --certs-tar ~/mycapsule.cexample.com-certs.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://sathost.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 /root/mycapsule.cexample.com-certs.tar to the system sathost.example.com
  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           "sathost.example.com"\
                    --foreman-proxy-register-in-foreman           "true"\
                    --foreman-proxy-foreman-base-url              "https://sathost.example.com"\
                    --foreman-proxy-trusted-hosts                 "sathost.example.com"\
                    --foreman-proxy-trusted-hosts                 "sathost.example.com"\
                    --foreman-proxy-oauth-consumer-key            "zTxifagZgudLwb9f7GGknmuHMN75pcLH"\
                    --foreman-proxy-oauth-consumer-secret         "LZapwnR4aabmgMPWSNaSBTY6BuPX7fXW"\
                    --foreman-proxy-content-pulp-oauth-secret     "awasWzeYcLTpMesvFUUfeE8gfLzjduUV"\
                    --foreman-proxy-content-certs-tar             "/root/mycapsule.cexample.com-certs.tar"\
                    --puppet-server-foreman-url                   "https://sathost.example.com"
  The full log is at /var/log/foreman-proxy-certs-generate.log


The above looks like a foreman version of the output with smartproxy and Katello references. Step 2 instructs to copy the certs.tar to the satellite server it is already on. Installer options also need review, --scenario foreman-proxy-content would fail with:

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.


Version-Release number of selected component (if applicable):
satellite-6.3.0-16.0.beta.el7sat.noarch

How reproducible:
always

Actual results:
Incorrect information displayed

Expected results:
Correct instructions
Comment 2 Ivan Necas 2017-08-08 08:34:01 UTC 

*** This bug has been marked as a duplicate of bug 1458749 ***
Note You need to log in before you can comment on or make changes to this bug.