Bug 1378115 - SSL/TLS documentation omits a critical step - copy CA to undercloud
Summary: SSL/TLS documentation omits a critical step - copy CA to undercloud
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 9.0 (Mitaka)
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 13:52 UTC by Ken Savich
Modified: 2019-04-17 16:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-24 13:23:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ken Savich 2016-09-21 13:52:03 UTC 
Description of problem:

ref: https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/director-installation-and-usage/appendix-a-ssl-tls-certificate-configuration

Section A.2 describes copying the generated CA cert to clients, but this needs to be copied to the undercloud node as well. Certificate generation will fail later on, thus causing installation of the undercloud to fail.

The step:

$ sudo cp ca.crt.pem /etc/pki/ca-trust/source/anchors/

needs to be completed on the undercloud node.

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

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Dan Macpherson 2016-09-21 14:15:53 UTC 
Hi Ken,

Thanks for the report. This is mentioned in the later section A.6. Using the Certificate with the Undercloud.

I might close this BZ since the information is already in the guide, but was there anything else in that appendix that seems out of place?
Comment 3 Ken Savich 2016-10-24 13:23:11 UTC 
Dan - sorry for the delay. Go ahead and close, I think this was an error on our side. 

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