Comment 0 for bug 1948621

There is a similar bug report already but closed with Invalid so filing a new one.
https://bugs.launchpad.net/charm-barbican-vault/+bug/1842058
Also it's worth noting that the previous bug was focused on HA setup including vip and such, but this time it's a non HA deployment on a test bed. It's not a one-off issue but sometimes happens.

cs:barbican-vault-27

Steps to reproduce:
1. juju deploy ./bundle.yaml
2. juju-wait -w --max_wait 4500 \
    --exclude vault \
    --exclude neutron-api-plugin-ovn \
    --exclude ovn-central \
    --exclude ovn-chassis \
    --exclude octavia \
    --exclude octavia-ovn-chassis \
    --exclude barbican-vault

3. juju run-action vault/leader --wait generate-root-ca

4. juju-wait -w --max_wait 1800 \
    --exclude octavia

Expected:
Step 4 completes without an error

Actual:
(Sometimes) Step 4 fails with timeout, and even after that barbican-vault is stuck indefinitely.