Bug 1726151 - capsule-certs-generate shows "foreman-installer --scenario foreman-proxy-content"
Summary: capsule-certs-generate shows "foreman-installer --scenario foreman-proxy-cont...
Keywords:
Status: CLOSED DUPLICATE of bug 1709761
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-02 08:44 UTC by Jan Hutař
Modified: 2019-07-02 08:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-02 08:55:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2019-07-02 08:44:57 UTC
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 ...

Comment 3 Jan Hutař 2019-07-02 08:48:44 UTC
Old similar/relevant BZ: bug 1458749

Comment 4 Evgeni Golov 2019-07-02 08:55:38 UTC

*** This bug has been marked as a duplicate of bug 1709761 ***


Note You need to log in before you can comment on or make changes to this bug.