Comment 10 for bug 1827668

As Aurelien has noted, this is now a consistent bug on mojo tests in designate-ha. I've run the test manually, and noticed that the mojo tests starts the vault unlocking script *before* keystone has finished it's final set of relation changes. This sort of confirms what Aurelien is saying.

Therefore, the strategy for the mojo tests (at least) is to work out why it thinks the model is ready, but keystone hasn't actually got to the stage of writing certificates; it's probably a change in keystone in delaying writing certificates (because they weren't available) but the mojo code still thinks it can copy stuff in.