Bug 1313057 - [RFE] Overcloud nodes deployed via Red Hat Director won't integrate their PAM/NSS with LDAP
Summary: [RFE] Overcloud nodes deployed via Red Hat Director won't integrate their PAM...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Linux
high
medium
Target Milestone: Upstream M3
: 12.0 (Pike)
Assignee: Angus Thomas
QA Contact: Prasanth Anbalagan
URL:
Whiteboard:
Depends On:
Blocks: 1339506 1442136 1468940
TreeView+ depends on / blocked
 
Reported: 2016-02-29 20:19 UTC by Pablo Caruana
Modified: 2019-12-16 05:27 UTC (History)
10 users (show)

Fixed In Version: python-novajoin-1.0.13-0.20170403154656.054c186.el7ost
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 20:40:44 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Pablo Caruana 2016-02-29 20:19:44 UTC
What problem/issue/behavior are you having trouble with?  What do you expect to see?

On the Overcloud, as deployed by Red Hat Director 7.2, seems to not be able to properly integrate (reconfigure) PAM/NSS to integrate with our current LDAP infrastructure. Is it possible to have Red Hat Director deploy Overcloud nodes configured so that authentication via PAM uses a LDAP back-end?

Comment 3 Mike Burns 2016-04-07 21:11:06 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 17 errata-xmlrpc 2017-12-13 20:40:44 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/RHEA-2017:3462


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