vault-charm

vault charm enters 'error' state sporadically

Bug #1939158 reported by Luciano Lo Giudice on 2021-08-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	vault-charm	Triaged	Medium	Unassigned

Bug Description

On a basic serverstack-on-openstack setup, the 'vault' charm will periodically (at random intervals) enter into an error state. Since many other charms depend on vault being operational, a large part of the setup gets blocked, which makes the whole system stumble and harder to debug.

Attached are the logs for the vault charm specifically at the time of the error, as well as a juju crash dump report. Further details can be provided as well.

In order to reproduce, it suffices to deploy the bundle specified at:
https://github.com/openstack-charmers/openstack-bundles/blob/master/stable/openstack-base/bundle.yaml

With the overlay:
https://github.com/openstack-charmers/openstack-bundles/blob/master/stable/overlays/openstack-base-virt-overlay.yaml

See original description

Tags:

Revision history for this message

Luciano Lo Giudice (lmlogiudice) wrote on 2021-08-06:

logs_and_crashdump.tar.gz Edit (13.1 MiB, application/x-tar)

Luciano Lo Giudice (lmlogiudice) on 2021-08-06

affects:

charm-guide → vault-charm

Luciano Lo Giudice (lmlogiudice) on 2021-08-06

description:	updated
description:	updated

Revision history for this message

Alex Kavanagh (ajkavanagh) wrote on 2021-08-10:

Judging by the logs, it's going into error state during update-status. As a rule, unless there is a programming error, charms ought not to go into error state during update-status, but should put the issue on the status line and optionally 'block'. In this case, this looks like a transient issue where the local vault isn't available during update-status.