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.

Bug 1482009

Summary: capsule-certs-generate offers a installer command with nonsense scenario
Product: Red Hat Satellite Reporter: Lukas Pramuk <lpramuk>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lukas Pramuk <lpramuk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-17 15:28:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Pramuk 2017-08-16 09:22:15 UTC 
Description of problem:
capsule-certs-generate offers a installer command with no scenario

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

How reproducible:
100%

Steps to Reproduce:

1. Generate capsule certs:

@SAT #capsule-certs-generate --foreman-proxy-fqdn cap.example.com --certs-tar ~/cap.example.com-certs.tar
root.com's password: 
stty: standard input: Inappropriate ioctl for device
Debug: Loading facts from /usr/share/foreman-insta: 0 00:00:00
Debug: Puppet::Type::Package::ProviderAptrpm: file: 0 0.0/s 00:00:03
Debug: Using settings: adding file resource 'ssldi: 0 0.0/s 00:00:04
Debug: Prefetching yum resources for package      : 0/18, 0%, 0.0/s, elapsed: 00:00:04
Package[katello-certs-tools]                      : 0/18, 0%, 0.0/s, elapsed: 00:00:05
File[/etc/pki/katello]                            : 1/18, 5%, 0.0/s, elapsed: 00:00:05
File[/etc/pki/katello/private]                    : 2/18, 11%, 0.0/s, elapsed: 00:00:05
File[/etc/pki/katello/certs]                      : 3/18, 16%, 0.0/s, elapsed: 00:00:05
File[/etc/pki/katello/private/katello-default-ca.p: 4/18, 22%, 0.0/s, elapsed: 00:00:05
Ca[katello-default-ca]                            : 5/18, 27%, 0.0/s, elapsed: 00:00:05
Ca[katello-server-ca]                             : 6/18, 33%, 0.0/s, elapsed: 00:00:05
File[/root/ssl-build/KATELLO-TRUSTED-SSL-CERT]    : 7/18, 38%, 0.0/s, elapsed: 00:00:05
Cert[cap.example.com-qpid-router-client]          : 8/18, 44%, 0.0/s, elapsed: 00:00:05
Cert[cap.example.com-apache]                      : 9/18, 50%, 1.7/s, elapsed: 00:00:06, ETA: 00:00:05
Cert[cap.example.com-qpid-client-cert]            : 10/18, 55%, 1.5/s, elapsed: 00:00:07, ETA: 00:00:05
Cert[cap.example.com-foreman-client]              : 11/18, 61%, 1.4/s, elapsed: 00:00:08, ETA: 00:00:04
Cert[cap.example.com-qpid-broker]                 : 12/18, 66%, 1.6/s, elapsed: 00:00:09, ETA: 00:00:03
Cert[cap.example.com-puppet-client]               : 13/18, 72%, 1.7/s, elapsed: 00:00:10, ETA: 00:00:02
Cert[cap.example.com-qpid-router-server]          : 14/18, 77%, 1.9/s, elapsed: 00:00:12, ETA: 00:00:02
Cert[cap.example.com-foreman-proxy-client]        : 15/18, 83%, 0.9/s, elapsed: 00:00:13, ETA: 00:00:03
Cert[cap.example.com-foreman-proxy]               : 16/18, 88%, 0.9/s, elapsed: 00:00:14, ETA: 00:00:02
Exec[generate /root/cap.example.com-certs.tar]    : 17/18, 94%, 0.9/s, elapsed: 00:00:15, ETA: 00:00:01
Done                                              : 18/18, 100%, 0.9/s, elapsed: 00:00:16
Done                                              : 18/18, 100%, 0.9/s, elapsed: 00:00:16
  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://sat.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/cap.example.com-certs.tar to the system cap.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           "sat.example.com"\
                    --foreman-proxy-register-in-foreman           "true"\
                    --foreman-proxy-foreman-base-url              "https://sat.example.com"\
                    --foreman-proxy-trusted-hosts                 "sat.example.com"\
                    --foreman-proxy-trusted-hosts                 "cap.example.com"\
                    --foreman-proxy-oauth-consumer-key            "eR9ZSpcAL2iuAFyVN7hfVuAaHWe2DccG"\
                    --foreman-proxy-oauth-consumer-secret         "bC7sYpLAPtduyBg2zPpSZB2e7q4A6g5W"\
                    --foreman-proxy-content-pulp-oauth-secret     "9EbFSaUb6PMqRqQo5o2ufC3iqHQ8pMuG"\
                    --foreman-proxy-content-certs-tar             "/root/cap.example.com-certs.tar"\
                    --puppet-server-foreman-url                   "https://sat.example.com"
  The full log is at /var/log/foreman-proxy-certs-generate.log


2. Try to run proposed installer command:

# satellite-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.


Actual results:
offered command fails

Expected results:
offered command succeeds
Comment 2 Lukas Pramuk 2017-08-17 15:28:36 UTC 

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