nova_wait_for_placement_service.py doesn't lookup the endpoint in the correct region

[Gauvain Pocentek]

We are deploying OpenStack in a multi-region setup: a first region is deployed as usual, the other regions are deployed without Kestone, and instead, they use the Keystone from the first region.

In that setup the nova_wait_for_placement_service.py script that runs in nova-compute containers might end up testing the wrong placement endpoint.

The deployment even fails if this endpoint doesn't exist (happens during the testing phase).

A solution is to explicitly get the endpoint for the region being deployed in the script.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/642035

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/642035
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=8948eced739a49ab2720810d0747a64012c8dd75
Submitter: Zuul
Branch: master

commit 8948eced739a49ab2720810d0747a64012c8dd75
Author: Gauvain Pocentek <email address hidden>
Date: Fri Mar 8 15:42:14 2019 +0100

    Test the correct placement endpoint with multiple regions

    In a multi-region setup (not yet supported but there are plans to
    support it) the nova_wait_for_placement_service.py script might check
    the wrong placement endpoint.

    This change makes the script explicitly look for the endpoint in the
    correct region.

    Change-Id: I83e44e0d0cb104dbb10b3699469e00e15b320409
    Closes-Bug: #1819174

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 10.5.0 release.