Relations remain Incomplete even after vault is ready

[John George]

While deploying an FCB cloud build including vault, ceph and nova-compute units report Incomplete relations with vault, even after vault has been configured according to:
https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-vault.html

The bundle, juju status and juju-crashdump are available here:
http://people.canonical.com/~jog/wp/

ceph-osd/0* waiting idle 0 10.22.130.98 Incomplete relation: vault

vault/0 active idle 1/lxd/6 10.22.131.89 8200/tcp Unit is ready (active: false, mlock: disabled)
  hacluster-vault/2 active idle 10.22.131.89 Unit is ready and clustered
vault/1* active idle 3/lxd/8 10.22.131.47 8200/tcp Unit is ready (active: true, mlock: disabled)
  hacluster-vault/0* active idle 10.22.131.47 Unit is ready and clustered
vault/2 active idle 4/lxd/9 10.22.131.74 8200/tcp Unit is ready (active: false, mlock: disabled)
  hacluster-vault/1 active idle 10.22.131.74 Unit is ready and clustered

[John George (jog)]

I've subscribed this bug to field-critical, since we're blocked during an on-site field deployment.

[James Page (james-page)]

authorize-charm was run on vault/0 which is not the lead unit - it needs to be run on vault/1.

The action will have failed with an appropriate error message.

[James Page (james-page)]

Raising docs task for charm-deployment-guide as this is not clear.

[James Page (james-page)]

Marking incomplete whilst bug reported tries running the action on the lead unit.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/641066

[John George (jog)]

Running the action against the leader resolved the issue.
Thank you for the quick response!

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/641066
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=471734c341635e61ec084b478f7abad8faf6d5de
Submitter: Zuul
Branch: master

commit 471734c341635e61ec084b478f7abad8faf6d5de
Author: James Page <email address hidden>
Date: Tue Mar 5 16:10:22 2019 +0000

    vault: ensure authorize-charm is run on lead unit

    Ensure its clear that the authorize-charm action should be run
    on the lead vault unit in a HA deployment by using the /leader
    syntax to auto-identify the lead unit.

    Add '--wait' parameter to example to ensure users see any action
    failures.

    Change-Id: I7dff6c3188d1877529e879adea4af9ffb8dee7c8
    Closes-Bug: 1818660