Comment 8 for bug 1661392

Spent a little more time on this today. It is a difficult race to solve on the g-s-s side due to the asynchronous nature of the glance-simplestreams-sync.sh run from cron. It can easily race and run with the wrong keystone IP information. This is a long running process that will not learn about changes to the configuration until its subsequent run.

In the future, we may consider changes to keystone (and the other APIs that run HA) to wait until hacluster is fully configured before running client relations. This will take some time.

In the meantime, there are two manual work arounds:
One, in the bundle set run to False until the deployment is complete. Then post-deploy set run to True. This guarantees g-s-s has the correct IP info for keystone before it produces the simplestreams data.
Two, set frequency to 1 hour and wait for at least one hour post deploy to test. The second run will have the correct keystone IP information.

I understand these are less than ideal, but they will get testing unblocked.