Bug 1394453

Summary: ospd8 installation documentation issues -- possible execution/procedure related bugs
Product: Red Hat OpenStack Reporter: Warren <wusui>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED DUPLICATE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: dmacpher, srevivo
Target Milestone: ---   
Target Release: ---   
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: 2016-12-12 04:14:32 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:

Description Warren 2016-11-12 07:08:07 UTC 
Description of problem:

https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/single/director-installation-and-usage/#appe-SSLTLS_Certificate_Configuration appears to not be correct in a few places.


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


How reproducible:
100% of the time

Steps to Reproduce:
1. Follow the instructions in the doc.

Actual results:

First off, all the issues in bugzilla 1385196 still happen in this case

In addition, the openstack user could not write to /etc/pki/CA/newcerts.
I manually changed its permission to 0777 (probably NOT recommended) just
to work around the problem.

Also, there is a definite documentation error.  The command:

openssl req  -key ca.key.pem -new -x509 -days 7300 -extensions v3_ca -out ca.crt.pem

and the command

openssl ca -config openssl.cnf -extensions v3_req -days 3650 -in server.csr.pem -out server.crt.pem -cert ca.cert.pem

refer to a file as ca.crt.pem and ca.cert.pem -- I think that it should be ca.cert.pem because that's what the openstack undercloud install operation expects later.
Comment 1 Dan Macpherson 2016-12-12 04:14:32 UTC 
Hi Warren,

I'm merging this BZ with BZ#1385196 and taking care of it in one go.

Closing this BZ as a duplicate.

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