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
I have validated that using proposed allows the machines to boot even
when Vault is sealed by rebooting all of the instances in a deployment
using vault + ceph-osd with encryption.
** Tags removed: verification-queens-needed
** Tags added: verification-queens-done
--
You received this bug
** Changed in: vaultlocker
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
** Tags added: uosci
--
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:
** Changed in: bionic-backports
Status: In Progress => 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
I've uploaded for bionic-backports and raised the associated bug task;
with regards to xenial, this will be delivered via the Ubuntu Cloud
Archive.
** Also affects: bionic-backports
Importance: Undecided
Status: New
** Changed in: bionic-backports
Status: New => In Progress
**
Would it be possible to backport the fix in Bionic (and maybe xenial, as
well, since they're both LTS)? Thank you.
--
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
This bug was fixed in the package vaultlocker - 1.0.3-0ubuntu1.18.10.1
---
vaultlocker (1.0.3-0ubuntu1.18.10.1) cosmic; 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
Hello Andrea, or anyone else affected,
Accepted vaultlocker into cosmic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/vaultlocker/1.0.3-0ubuntu1.18.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
This bug was fixed in the package vaultlocker - 1.0.3-0ubuntu2
---
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
Thanks James for following up on this. Will the fix trickle down to
Bionic and Xenial as well? We have deployments that use vault on both
releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Uploaded to disco development and to cosmic UNAPPROVED for SRU team
review.
** Changed in: vaultlocker (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: vaultlocker (Ubuntu Disco)
Assignee: (unassigned) => James Page (james-page)
** Changed in: vaultlocker (Ubuntu
unsealing of vault that is.
--
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:
As a temporary workaround:
juju run --application ceph-osd "sudo sed -i /Before=/d
/lib/systemd/system/vaultlocker-decrypt@.service"
will update the systemd unit inline with the proposed SRU and allow a
full cloud reboot with vaultlocker in use.
Timely unsealing of vaultlocker is also needed
Proposed fix appears to have the desired effect.
** Changed in: vaultlocker
Status: In Progress => Fix Committed
** Description changed:
+ [Impact]
+ decrypt of vaultlocker encrypted block devices blocks the
network-online.target; this means that if vault is hosted on the same hardware
Reproduced by power cycling a converged deployment; the Before=network-
online.target stanza in vaultlocker-decrypt causes the boot to block.
** Also affects: vaultlocker (Ubuntu)
Importance: Undecided
Status: New
** Changed in: vaultlocker (Ubuntu)
Status: New => Triaged
**
Raised:
https://github.com/openstack-charmers/vaultlocker/pull/4
--
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
Marking charm task as invalid as this is a vaultlocker issue.
** Also affects: vaultlocker
Importance: Undecided
Status: New
** Changed in: vaultlocker (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: vaultlocker (Ubuntu Cosmic)
Importance: Undecided => High
** Changed
18 matches
Mail list logo
