Bug 1677001 - Enable TLS-Everywhere when IdM is not on the ctlplane network
Summary: Enable TLS-Everywhere when IdM is not on the ctlplane network
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z2
: 14.0 (Rocky)
Assignee: Emilien Macchi
QA Contact: Pavan
URL:
Whiteboard:
Depends On: 1661635
Blocks: 1655185 1677003
TreeView+ depends on / blocked
 
Reported: 2019-02-13 18:24 UTC by Harry Rybacki
Modified: 2019-06-11 12:21 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.2.1-0.20190119154865.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, when using TLS Everywhere, your controller node was required to access IdM through the `ctlplane` network. As a result, if traffic was routed through a different network, then the overcloud deployment process would fail due to `getcert` errors. To address this, IdM enrolment has been moved into a composable service that runs within `host_prep_tasks`; this runs at the start of the deployment phase. Note that the script will simply exit if the instance has already been enrolled in IdM.
Clone Of: 1661635
: 1677003 (view as bug list)
Environment:
Last Closed: 2019-04-30 17:51:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 638521 0 None None None 2019-02-28 15:31:46 UTC
Red Hat Product Errata RHBA-2019:0878 0 None None None 2019-04-30 17:51:23 UTC

Comment 1 Harry Rybacki 2019-02-28 15:31:47 UTC
Up and downstream code has merged. Moving bug to POST.

Comment 2 Harry Rybacki 2019-02-28 16:21:28 UTC
Downstream build complete. Moving but to MODIFIED.

Comment 10 errata-xmlrpc 2019-04-30 17:51:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0878


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