vault-charm

Vault health check failed

Bug #2072343 reported by Amjad Chami
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vault-charm
Incomplete
Undecided
Unassigned

Bug Description

Solutions qa ran into a bug with vault 1.8/ Stable where the deployment fails because
"Vault health check failed" and in the logs there's
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='127.0.0.1', port=8220): Max retries exceeded with url: /v1/sys/health (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fac3304c970>: Failed to establish a new connection: [Errno 111] Connection refused'))

Link to run: https://solutions.qa.canonical.com/testruns/0ea93d6b-4bfa-4111-ad5e-3977cb554b52
Link to artifacts: https://solutions.qa.canonical.com/testruns/0ea93d6b-4bfa-4111-ad5e-3977cb554b52

Revision history for this message
Jadon Naas (jadonn) wrote :

I think this issue is probably from a transient infrastructure issue that impacted that particular vault/1 unit. Do you have any more log information from the Vault service running on vault/1? It looks like the Vault service was not running on vault/1.

Changed in vault-charm:
status: New → Incomplete
Revision history for this message
Abdullah (motjuste) wrote :

You can find more identified occurrences of this bug at : https://solutions.qa.canonical.com/bugs/lp:vault:2072343

For example, it was observed in this run: <https://solutions.qa.canonical.com/testruns/54ff6bd3-53ad-4d4f-8f1c-7aae7cf4eb9f>, and the relevant crashdump may be found by following the link at the bottom of the page leading to <https://oil-jenkins.canonical.com/artifacts/54ff6bd3-53ad-4d4f-8f1c-7aae7cf4eb9f/index.html>, and looking particularly into the crashdump <https://oil-jenkins.canonical.com/artifacts/54ff6bd3-53ad-4d4f-8f1c-7aae7cf4eb9f/generated/generated/kubernetes-maas/juju-crashdump-kubernetes-maas-2024-07-14-06.27.36.tar.gz>

Revision history for this message
Marian Gasparovic (marosg) wrote :

We hit it again in this run
https://solutions.qa.canonical.com/testruns/a9555a05-5ba1-4ff2-9562-af6dfcfbd1cd/

Changed in vault-charm:
status: Incomplete → New
Revision history for this message
Felipe Reyes (freyes) wrote :

What are the expectations around this bug?, because healthcheck failure is associated to a 'Connection refused' error, this could mean many things, as Jadon mentioned this could have been triggered during resource contentions issues in the hypervisor. Have you checked the overall healthiness of the environment?

Changed in vault-charm:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.