This bug was fixed in the package vaultlocker -
1.0.4-0ubuntu0.19.04.1~ubuntu18.04.1~cloud0
---------------
vaultlocker (1.0.4-0ubuntu0.19.04.1~ubuntu18.04.1~cloud0) xenial-queens;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
vaultlocker (1.0.4-0ubuntu0.19.04.1~ubuntu18.04.1) bionic-backports;
urgency=medium
.
* No-change backport to bionic
.
vaultlocker (1.0.4-0ubuntu0.19.04.1) disco; urgency=medium
.
* New upstream point release including fix for an issue when
vaultlocker blocks boot if interfaces are in a down or no-carrier
state (LP: #1838607):
- d/p/*: Drop, all included in new point release.
.
vaultlocker (1.0.3-0ubuntu2) disco; urgency=medium
.
* d/p/unblock-network.online.target.patch: Cherry pick fix to ensure
that vaultlocker-decrypt@ systemd units don't block the network-online
target which blocks server boot in the event that the Vault deployment
being used is not accessible (LP: #1818680).
.
vaultlocker (1.0.3-0ubuntu1) cosmic; urgency=medium
.
* Initial release.
** Changed in: cloud-archive/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818680
Title:
booting should succeed even if vault is unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/bionic-backports/+bug/1818680/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
