vault charm gives permission denied running authorize-charm action
Bug #1779875 reported by
Chris Procter
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vault-charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have a 3 node HA clustered vault installation.
Following the instructions to authorize the vault charm at https:/
On the leader I ran:
export VAULT_TOKEN=[root token]
vault token create -use-limit=1 -ttl=10m
then on the juju node ran
juju run-action vault/0 authorize-charm token=[generated token]
The action resulted in:
ubuntu@
message: permission denied
status: failed
repeated runs with newly generated tokens produce the same result.
This is consistant across reinstallations of the cluster
tags: | added: cpe-onsite |
information type: | Public → Public Security |
information type: | Public Security → Public |
To post a comment you must log in.
ubuntu@ juju-a9b1a9- 12-lxd- 15:~$ export VAULT_TOKEN= 458edd7b- cb35-366f- cb37-805210dbde 29 juju-a9b1a9- 12-lxd- 15:~$ vault token create -use-limit=1 -ttl=10m f784-aa68- 4c64-941a32ac2b 92 aa0c-8a6b- 21a3-6d83706690 13 juju-a9b1a9- 12-lxd- 15:~$ exit fnos-inf02: ~$ juju run-action vault/1 authorize-charm token=4dd9f7fc- f784-aa68- 4c64-941a32ac2b 92 e0e2-4af6- 8a09-49f5e21134 33 fnos-inf02: ~$ juju show-action-output 540a5d76- e0e2-4af6- 8a09-49f5e21134 33
ubuntu@
Key Value
--- -----
token 4dd9f7fc-
ken_accessor 3c09dd08-
token_duration 10m
token_renewable true
token_policies [root]
ubuntu@
logout
Connection to 172.17.20.214 closed.
ubuntu@
Action queued with id: 540a5d76-
ubuntu@
message: permission denied
status: failed
timing:
completed: 2018-07-03 13:28:05 +0000 UTC
enqueued: 2018-07-03 13:28:01 +0000 UTC
started: 2018-07-03 13:28:01 +0000 UTC