Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

Fix Vault client having auth timeout #7

Merged
merged 1 commit into from Sep 18, 2019

Conversation

johnsca
Copy link
Contributor

@johnsca johnsca commented Sep 18, 2019

The auth token received when doing the auth_approle() only lasts for 60s. When the charm hook takes longer than that to complete, the atexit handler for updating the hashes will fail with "permission denied" due to the auth timeout.

Fixes: lp:1843809

The auth token received when doing the `auth_approle()` only lasts for
60s.  When the charm hook takes longer than that to complete, the atexit
handler for updating the hashes will fail with "permission denied" due
to the auth timeout.

Fixes: https://bugs.launchpad.net/charm-kubernetes-master/+bug/1843809
@johnsca
Copy link
Contributor Author

johnsca commented Sep 18, 2019

Tested on AWS along with:

Confirmed that the cluster blocked until Vault was manually unsealed, then successfully came up. Then confirmed that the relation was able to be removed without error.

@tvansteenburgh tvansteenburgh merged commit 0c711dd into master Sep 18, 2019
@tvansteenburgh tvansteenburgh deleted the bug/lp/1843809/client-auth-timeout branch September 18, 2019 15:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants