Fail to configure Vault Enterprise
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.4 |
Won't Fix
|
Medium
|
Unassigned | |||
3.5 |
Won't Fix
|
Medium
|
Unassigned | |||
3.6 |
Triaged
|
Medium
|
Unassigned |
Bug Description
`sudo maas config-vault configure ....` always fails due to `CommandError: permission denied`.
Steps to reproduce:
1) get a vault ENTERPRISE server https:/
2) configure the vault according to https:/
3) at the step 5 of the guide, run `vault write -wrap-ttl=60m -force auth/approle/
4) the command `sudo maas config-vault configure $URL $APPROLE_ID $WRAPPED_TOKEN $SECRETS_PATH --mount $SECRET_MOUNT` fails with `CommandError: permission denied...`
no longer affects: | maas/3.4 |
Problem is that we are creating the hvac client https:/ /git.launchpad. net/maas/ tree/src/ maasserver/ vault.py# n83 without any parameter, which results in permission denied of course.