Bug 1626106

Summary:	capsule-certs-generate wrong example in output
Product:	Red Hat Satellite	Reporter:	Jan Jansky <jjansky>
Component:	Certificates	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	chrobert, ehelms, jjansky
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-11 15:13:30 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 Jan Jansky 2018-09-06 15:04:18 UTC

Description of problem: When i generate certificates for capsule it will show me example:

How reproducible:
Always

Steps to Reproduce:
1. Execute capsule-cert-generate --foreman-proxy-fqdn capsule.example.com --certs-tar capsule.example.com.tar

Actual results:

2. Copy the following file /var/www/html/capsule.example.com.tar to the system capsule.example.com at the following location /root/capsule.example.com.tar
  scp /var/www/html/capsule.example.com.tar root.com:/root/capsule.example.com.tar

  satellite-installer --scenario capsule\
                      --foreman-proxy-content-parent-fqdn           "capsule.example.com"\
                      --foreman-proxy-register-in-foreman           "true"\
                      --foreman-proxy-foreman-base-url              "https://satellite.example.com"\
                      --foreman-proxy-trusted-hosts                 "satellite.example.com"\
                      --foreman-proxy-trusted-hosts                 "capsule.example.com"\
                      --foreman-proxy-oauth-consumer-key            "naLCzcg7jU7txiGRhpJrttqZu9dnxBFR"\
                      --foreman-proxy-oauth-consumer-secret         "X2yWcSbsmQ6P5ob6QcuE6wzJ8ET3nd4f"\
                      --foreman-proxy-content-certs-tar             "/var/www/html/capsule.example.com.tar"\
                      --puppet-server-foreman-url                   "https://satellite.example.com"



Expected results:
option a)
scp /var/www/html/capsule.example.com.tar root.com:/root/capsule.example.com.tar

and 

                      --foreman-proxy-content-certs-tar             "/root/capsule.example.com.tar"\

option b)
scp /var/www/html/capsule.example.com.tar root.com:/var/www/html/capsule.example.com.tar

and 

                      --foreman-proxy-content-certs-tar             "/var/www/html/capsule.example.com.tar"\


Additional info:
Personally like more option a

Comment 4 Jan Jansky 2018-09-10 07:14:44 UTC

Hello Chris,

actual full output

cd /home
capsule-certs-generate --foreman-proxy-fqdn capsule.example.com --certs-tar capsule.example.com.tar
Resetting puppet server version param...
Installing             Done                                               [100%] [................................................................................................................................]
  Success!

ATTENTION. For Capsule upgrades:
  Please see official documentation for steps and parameters to use when upgrading a 6.3 Capsule to 6.4.

  To finish the installation, follow these steps:

  If you do not have the Capsule registered to the Satellite instance, then please do the following:

  1. yum -y localinstall http://sat64betatest.usersys.redhat.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 Capsule installation:

  1. Ensure that the satellite-capsule package is installed on the system.
  2. Copy the following file /home/capsule.example.com.tar to the system capsule.example.com at the following location /root/capsule.example.com.tar
  scp /home/capsule.example.com.tar root.com:/root/capsule.example.com.tar
  3. Run the following commands on the Capsule (possibly with the customized
     parameters, see satellite-installer --scenario capsule --help and
     documentation for more info on setting up additional services):

  satellite-installer --scenario capsule\
                      --foreman-proxy-content-parent-fqdn           "sat64betatest.usersys.redhat.com"\
                      --foreman-proxy-register-in-foreman           "true"\
                      --foreman-proxy-foreman-base-url              "https://sat64betatest.usersys.redhat.com"\
                      --foreman-proxy-trusted-hosts                 "sat64betatest.usersys.redhat.com"\
                      --foreman-proxy-trusted-hosts                 "capsule.example.com"\
                      --foreman-proxy-oauth-consumer-key            "naLCzcg7jU7txiGRhpJrttqZu9dnxBFR"\
                      --foreman-proxy-oauth-consumer-secret         "X2yWcSbsmQ6P5ob6QcuE6wzJ8ET3nd4f"\
                      --foreman-proxy-content-certs-tar             "/home/capsule.example.com.tar"\
                      --puppet-server-foreman-url                   "https://sat64betatest.usersys.redhat.com"



Requested output

ATTENTION. For Capsule upgrades:
  Please see official documentation for steps and parameters to use when upgrading a 6.3 Capsule to 6.4.

  To finish the installation, follow these steps:

  If you do not have the Capsule registered to the Satellite instance, then please do the following:

  1. yum -y localinstall http://sat64betatest.usersys.redhat.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 Capsule installation:

  1. Ensure that the satellite-capsule package is installed on the system.
  2. Copy the following file /home/capsule.example.com.tar to the system capsule.example.com at the following location /root/capsule.example.com.tar
  scp /home/capsule.example.com.tar root.com:/root/capsule.example.com.tar
  3. Run the following commands on the Capsule (possibly with the customized
     parameters, see satellite-installer --scenario capsule --help and
     documentation for more info on setting up additional services):

  satellite-installer --scenario capsule\
                      --foreman-proxy-content-parent-fqdn           "sat64betatest.usersys.redhat.com"\
                      --foreman-proxy-register-in-foreman           "true"\
                      --foreman-proxy-foreman-base-url              "https://sat64betatest.usersys.redhat.com"\
                      --foreman-proxy-trusted-hosts                 "sat64betatest.usersys.redhat.com"\
                      --foreman-proxy-trusted-hosts                 "capsule.example.com"\
                      --foreman-proxy-oauth-consumer-key            "naLCzcg7jU7txiGRhpJrttqZu9dnxBFR"\
                      --foreman-proxy-oauth-consumer-secret         "X2yWcSbsmQ6P5ob6QcuE6wzJ8ET3nd4f"\
                      --foreman-proxy-content-certs-tar             "/root/capsule.example.com.tar"\
                      --puppet-server-foreman-url                   "https://sat64betatest.usersys.redhat.com"

In summary, if you execute capsule-certs-generate for example in /home with parameters --certs-tar capsule.example.com.tar it will create tar as /home/capsule.example.com.tar.

Output says you to scp tar to capsule into root (as below), which is correct

  scp /home/capsule.example.com.tar root.com:/root/capsule.example.com.tar

but then it will tell you to use parameter for tar from /home (as below), which will fail because tar was copied to /root and not /home.

                      --foreman-proxy-content-certs-tar             "/home/capsule.example.com.tar"\

Comment 5 Eric Helms 2018-09-11 15:13:30 UTC


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