I've uploaded a new point release of vaultlocker for consideration for SRU; the point release includes only two changes - a previous fix that was already included as a patch (1.0.3-0ubuntu2) and the fix for this issue.
** Description changed: + [Impact] + Systems with block device encryption managed using vaultlocker will not boot if any interfaces are in a DOWN or NO-CARRIER state + + [Test Case] + Deploy OpenStack with block device encryption using vaultlocker (charms) + Unplug or disable a network interface which is configured on the system. + Reboot - server will timeout on unlocking block devices on boot. + + [Regression Potential] + Low - change simply removes the dependency on systemd-networkd-wait-online; the vaultlocker units still start after networking.service and the daemon will retry to connect to vault if the require network interface has not yet started. + + [Original Bug Report] On some hosts, it might be possible to have interfaces that are DOWN with NO-CARRIER. In this case, systemd-networkd-wait-online will timeout and fail. Therefore vaultlocker will also fail. If vaultlocker fails it might impact the mount of the encrypted partitions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838607 Title: vaultlocker service fails when some interface are DOWN with NO-CARRIER To manage notifications about this bug go to: https://bugs.launchpad.net/bionic-backports/+bug/1838607/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
