The issue seems to be a race condition that depends on relative ordering of keystone relation-scoped events and is reproducible in two cases:
1) set up a cloud without https and add "certificates" relation to vault later;
2) set up a cloud with "certificates" relations right away and unlock vault after the model mostly settles.
Subscribed ~field-high.
The issue seems to be a race condition that depends on relative ordering of keystone relation-scoped events and is reproducible in two cases:
1) set up a cloud without https and add "certificates" relation to vault later;
2) set up a cloud with "certificates" relations right away and unlock vault after the model mostly settles.