Comment 25 for bug 1818113

The crashdump from comment #13 shows octavia trying to communicate with other
services once it has received credentials from keystone. Looking at the logs
all octavia units fail running setup_hm_port at around 11:48. But looking at
the keystone log at the same time keystone/0 and keystone/2 have yet to
setup their database connection and are still talking to their local sqllite
db, this results in them returning a 500 error.

Looking at the keystone charm it delays advertising client credentials until
it is ready. Unfortunately it only checks its own readiness and not that of its
peers. This can lead to the situation from comment #13 where only one keystone
unit is able to service requests so there is a 2 in 3 chance of getting a 500
back.