Keystone admin port exposure change broke backwards compatibility

[Juan Antonio Osorio Robles]

The following series of commits https://review.openstack.org/#/q/I79563f62fd49a4f7654779157ebda3c239d6dd22 broke backwards compatibility for the newton branch which some folks were using in production. It did so since some folks had external plugins that relied on the keystone admin port being exposed to the public network. In order to keep these use-cases working, while folks migrate to using keytone v3, we need to re-expose the keystone admin endpoint.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/543431

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/543431
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=5618a274179bc6497d2a4478ce763eb91ecacf0b
Submitter: Zuul
Branch: stable/newton

commit 5618a274179bc6497d2a4478ce763eb91ecacf0b
Author: Juan Antonio Osorio Robles <email address hidden>
Date: Mon Feb 12 13:26:15 2018 +0200

    Make exposing the keystone admin port optional

    A recent commit [1] removed the exposure of the keystone admin port for
    the public interface. While this removal was intended, it was not ideal
    to backport it to stable/newton as some folks were relying on this port
    being available.

    This commit then adds a flag to expose or hide the keystone admin
    endpoint from the public network. It's on by default to keep the
    functionality that folks with newton were seeing; but it lets folks opt
    out of it if needed (as is the case is some deployments).

    [1] I79563f62fd49a4f7654779157ebda3c239d6dd22

    Closes-Bug: #1748872
    Change-Id: I865aff9d54ebbe6acc44ffca41c951a05da71218

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-tripleo 5.6.9 release.