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 1569084 - capsule-certs-generate suggests scp-ing tarball to Satellite, not to future Capsule
Summary: capsule-certs-generate suggests scp-ing tarball to Satellite, not to future C...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-18 15:08 UTC by Pavel Moravec
Modified: 2018-04-20 14:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-20 06:42:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pavel Moravec 2018-04-18 15:08:14 UTC 
Description of problem:
capsule-certs-generate wrongly suggests where to scp the tarball with certificates - in the step 2. below "Once this is completed", it tells to scp the tarball to the Satellite itself, instead of to the future Capsule, see:

[root@pmoravec-sat63 ~]# hostname -f
pmoravec-sat63.gsslab.brq2.redhat.com
[root@pmoravec-sat63 ~]# capsule-certs-generate --node-fqdn pmoravec-caps63.gsslab.brq2.redhat.com --certs-tar=pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar
Installing             Done                                               [100%] [...........................................................................................................]
  Success!
..
  2. Copy the following file /root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar to the system pmoravec-sat63.gsslab.brq2.redhat.com at the following location /root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar
  scp /root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar root.brq2.redhat.com:/root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar
..

"to the system <capsule-not-satellite>" and "root@<capsule-not-satellite>:" should be there.


Version-Release number of selected component (if applicable):
satellite-6.3.1-3.el7sat.noarch
satellite-installer-6.3.0.12-1.el7sat.noarch


How reproducible:
100%


Steps to Reproduce:
1. Run on Satellite:

CAPSULE=whatever.fqdn.you.come.up
capsule-certs-generate --node-fqdn $CAPSULE --certs-tar=${CAPSULE}-certs.tar 2>&1 | grep "root@${CAPSULE}"


Actual results:
no output


Expected results:
the scp command should be on output


Additional info:
Comment 1 Brad Buckingham 2018-04-19 16:47:55 UTC 
Hey Chris,

Do you know if this may be a duplicate?  I recall there being other reports of incorrect output on capsule-certs-generate, but do not see one specifically for this.
Comment 2 Pavel Moravec 2018-04-20 06:42:46 UTC 
Mea culpa, I used wrong parameter --node-fqdn instead of --foreman-proxy-fqdn . Using the prior one, I cant even install Capsule as the tarball lacks certificates :) and using the later one, proper scp command etc. is shown:

capsule-certs-generate --foreman-proxy-fqdn pmoravec-caps63.gsslab.brq2.redhat.com --certs-tar=pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar
..
  2. Copy the following file /root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar to the system pmoravec-caps63.gsslab.brq2.redhat.com at the following location /root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar
  scp /root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar root.brq2.redhat.com:/root/pmoravec-caps63.gsslab.brq2.redhat.com-certs.tar
..

Docs is clear here, purely human error.
Note You need to log in before you can comment on or make changes to this bug.