Bug 1567895 - Unclear instructions on backing up the certificates on the undercloud node when using ssl in the undercloud
Summary: Unclear instructions on backing up the certificates on the undercloud node wh...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-16 11:38 UTC by Punit Kundal
Modified: 2018-08-30 12:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-30 12:31:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Punit Kundal 2018-04-16 11:38:43 UTC
Description of problem:

The Documentation at [1] Section 2.3 "Back Up the Undercloud" mentions the below when it comes to backing up the certificates:

+++
 The undercloud SSL certificates:

    /etc/pki/ca-trust/source/anchors/ca.crt.pem
    /home/stack /etc/pki/instack-certs/undercloud.pem 
+++

However the SSL operations are performed at the haproxy level and the actual location of the certificates is:

+++
listen zaqar_api
  bind X.X.X.X:13888 transparent ssl crt /etc/pki/tls/certs/undercloud-X.X.X.X.pem
  bind X.X.X.X:8888 transparent
  mode http
  server X.X.X.X X.X.X.X:8888 check fall 5 inter 2000 rise 2
+++


Can we please have this documentation carefully reviewed and updated accordingly  ?

It is noted that the documentation is already under a review and should be updated accordingly. However the customer would like to ensure that this is covered in the documentation and hence the bugzilla is being opened.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


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