Comment 1 for bug 1915853

I can reproduce the bug with the simple clustered vault setup

$ juju run-action --wait vault/4 authorize-charm token=s.Fz4eOtkZXi2hmM7xEbdydWrx
unit-vault-4:
  UnitId: vault/4
  id: "8"
  message: 'subprocess.CalledProcessError: Command ''[''leader-set'', ''local-charm-access-id=c220509c-043e-e450-9231-2e3063cd8886'']''
    returned non-zero exit status 1.'
  results:
    Stderr: |
      ERROR cannot write leadership settings: cannot write settings: not the leader
  status: failed
  timing:
    completed: 2021-02-19 16:14:24 +0000 UTC
    enqueued: 2021-02-19 16:14:19 +0000 UTC
    started: 2021-02-19 16:14:22 +0000 UTC

It seems the leader checker is not working correctly in this case for authorize-charm action. Will investigate further.