vault crashed without any interaction with user

Bug #1918718 reported by Dariusz Smigiel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Undecided
Unassigned
vault-charm
Fix Released
Undecided
Unassigned

Bug Description

I deployed OpenStack using juju, via [openstack bundle][3]

The Cloud has been working for couple days. It's been deployed: 2021-03-09 21:23:17
No activity was happening for last couple days.

When I looked at `juju status` around 2021-03-11 15:46:38 I found out that `juju status` is reporting error on `vault/0` unit.
```
vault/0* error idle 24 10.5.0.14 8200/tcp hook failed: "update-status"
  vault-mysql-router/0* active idle 10.5.0.14 Unit is ready
```

Please see attached [logs][1] from `/var/log/juju/unit-vault-0.log`. The event which caused outage started around 2021-03-11 03:47:20

At first I suspected autoupdate problem, but it doesn't seem to be [the case][2].

The issue has been fixed by running `juju resolved vault/0`

When I went through `/var/log/syslog` for `vault/0` I noticed possible [culprit][4]

Deployed with:
```
ubuntu@smigiel-dariusz-bastion:~$ juju version
2.8.9-bionic-amd64
ubuntu@smigiel-dariusz-bastion:~$ juju ssh vault/0 lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
Connection to 10.5.0.14 closed.
ubuntu@smigiel-dariusz-bastion:~$ juju ssh nova-compute/0 nova-manage --version
22.0.1
```

[1]: https://paste.ubuntu.com/p/RksTmRCpCW/
[2]: https://paste.ubuntu.com/p/FcnvN7QZfN/
[3]: https://github.com/openstack-charmers/openstack-bundles/blob/master/stable/openstack-base/bundle.yaml
[4]: https://paste.ubuntu.com/p/C3zxd2pmpc/

Revision history for this message
David Ames (thedac) wrote :

This is not a juju bug. It may or may not be a vault charm bug. We need more information to determine that.

A jujucrashdump would be helpful

Changed in juju:
status: New → Invalid
Changed in vault-charm:
status: New → Incomplete
Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :

Marking as invalid. I neither can reproduce this error nor provide crashdump.
I believe I misunderstood what happened here.

Changed in vault-charm:
status: Incomplete → Invalid
Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :
Changed in vault-charm:
status: Invalid → Fix Released
Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :

I've noticed this bug again. This time I tracked down the source of this bug. Bugfix for it has been released already as #1886083 and is part of `master` branch.
I'm using latest/stable version == 21.01.

21.01:
https://github.com/openstack/charm-vault/blob/stable/21.01/src/reactive/vault_handlers.py#L793
master:
https://github.com/openstack/charm-vault/blob/master/src/reactive/vault_handlers.py#L806

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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