[Bug 1818680] Re: booting should succeed even if vault is unavailable
james.page at ubuntu.com
Tue Dec 10 15:18:34 UTC 2019
** Changed in: vaultlocker
Status: Fix Committed => Fix Released
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
booting should succeed even if vault is unavailable
Status in Bionic Backports:
Status in OpenStack ceph-osd charm:
Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive queens series:
Status in vaultlocker:
Status in vaultlocker package in Ubuntu:
Status in vaultlocker source package in Cosmic:
Status in vaultlocker source package in Disco:
decrypt of vaultlocker encrypted block devices blocks the network-online.target; this means that if vault is hosted on the same hardware which is using vaultlocker for encryption at rest, the server will fail to boot fully in the event that all servers are rebooted at the same time.
Power cycle all servers
Servers never get to multiuser.target as vaultlocker-decrypt services block network-online.target so LXD containers never get started.
The proposed fix drops the Before=network-online.target stanza from the vaultlocker-decrypt systemd unit so minimal impact.
[Original bug report]
If ceph is using vault secrets to encrypt its volumes and vault is not available, booting is not possible without manual intervention, as the ceph-volume and vaultlocker-decrypt services will hang forever.
In case of a full cloud outage, bootstrapping the mysql and vault nodes will require quite a bit of manual intervention, as all required nodes will have to be booted in single user mode to bypass the volume decryption services.
Decryption of the ceph volumes should instead timeout, and allow the
rest of the machine to complete the boot sequence.
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs