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 1399377 - [Ref-Arch] Section 5.2.1.7 Multi-hosts Certificate for Virtual Capsule Server- sat6ha-lb-refarch.pdf
Summary: [Ref-Arch] Section 5.2.1.7 Multi-hosts Certificate for Virtual Capsule Serve...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks: Sat6_HA_Tracker
TreeView+ depends on / blocked
 
Reported: 2016-11-28 22:43 UTC by Ash Westbrook
Modified: 2020-12-14 07:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-23 05:18:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Changed script to use satellite-installer (1.22 KB, text/plain)
2016-11-28 22:43 UTC, Ash Westbrook 		no flags Details
View All

Description Ash Westbrook 2016-11-28 22:43:53 UTC 
Created attachment 1225502 [details]
Changed script to use satellite-installer

Description of problem:

Script given in section 5.2.1.7  Multi-hosts Certificate for Virtual Capsule Serve uses katello-installer instead of satellite-installer. This causes the script to fail:

[root@satqc-ha ~]# /root/katello-multi-host-certs.sh  <fqdn> <capsule fqdn> <capsule fqdn>

ERROR: these arguments make no sense in this context (try --help): ['$set_cname']
ERROR: katello-installer is no longer used.  Please use 'satellite-installer --scenario satellite'.
       For more information on available options, include '--help'.
/root/katello-multi-host-certs.sh: line 25: --certs-server-cert-req: command not found
/root/katello-multi-host-certs.sh: line 27: <fqdn>/custom-cert.crt.req: No such file or directory
/root/katello-multi-host-certs.sh: line 28: --certs-server-key: command not found
/root/katello-multi-host-certs.sh: line 31: --certs-server-ca-cert: command not found
/root/katello-multi-host-certs.sh: line 33: /root/ssl-build/katello-default-ca.crt: Permission denied
/root/katello-multi-host-certs.sh: line 34: --certs-update-server: command not found
Preparing installation Done                                              
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/capsule-certs-generate.log
/root/katello-multi-host-certs.sh: line 41: <fqdn>/custom-cert.crt: No such file or directory
/root/katello-multi-host-certs.sh: line 43: <fqdn>/custom-cert.crt.req: No such file or directory
/root/katello-multi-host-certs.sh: line 45: <fqdn>/custom-cert.key: No such file or directory
/root/katello-multi-host-certs.sh: line 47: /root/ssl-build/katello-default-ca.crt: Permission denied

Version-Release number of selected component (if applicable):

Satellite 6.2.1

How reproducible:

Always


Actual results:

Failure even if command is changed to satellite-installer rather than katello-installer:

[root@satqc-ha ~]# /root/satellite-multi-host-certs.sh  <fqdn> <fqdn capsule> <fqdn capsule>
ERROR: these arguments make no sense in this context (try --help): ['$set_cname']
Preparing installation Done                                              
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/foreman-installer/satellite.log
/root/satellite-multi-host-certs.sh: line 25: --certs-server-cert-req: command not found
/root/satellite-multi-host-certs.sh: line 27: <fqdn>/custom-cert.crt.req: No such file or directory
/root/satellite-multi-host-certs.sh: line 28: --certs-server-key: command not found
/root/satellite-multi-host-certs.sh: line 31: --certs-server-ca-cert: command not found
/root/satellite-multi-host-certs.sh: line 33: /root/ssl-build/katello-default-ca.crt: Permission denied
/root/satellite-multi-host-certs.sh: line 34: --certs-update-server: command not found
Preparing installation Done                                              
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/capsule-certs-generate.log
/root/satellite-multi-host-certs.sh: line 41: <fqdn>/custom-cert.crt: No such file or directory
/root/satellite-multi-host-certs.sh: line 43: <fqdn>/custom-cert.crt.req: No such file or directory
/root/satellite-multi-host-certs.sh: line 45: <fqdn>/custom-cert.key: No such file or directory
/root/satellite-multi-host-certs.sh: line 47: /root/ssl-build/katello-default-ca.crt: Permission denied

[root@satqc-ha ~]# ls -l /root/ssl-build/katello-default-ca.crt
-rw-r--r--. 1 root root 5459 Oct 11 17:53 /root/ssl-build/katello-default-ca.crt

Expected results:

Should succeed

Additional info:

Attached scripts


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:
Comment 1 Balaji 2016-11-29 21:18:27 UTC 
Thanks for the information. Will update the doc in the next version.
Comment 3 Balaji 2017-02-15 16:46:59 UTC 
Please close this as it is being addressed in the next update of the reference architecture document.
Comment 4 Andrew Dahms 2017-02-15 23:12:18 UTC 
Closing in accordance with comment #3.
Comment 12 Andrew Dahms 2018-07-23 05:18:52 UTC 
This bug was raised against the document "Deploying a Highly Available Red Hat Satellite Server 6 Environment", for which customers are now being asked to contact Red Hat (either their account team or consulting team) directly for assistance.

Because the product documentation team is unable to process this request, and in consultation with the Reference Architecture team, I am now closing this bug.

See the following article for more information -

https://access.redhat.com/solutions/1603283
Note You need to log in before you can comment on or make changes to this bug.