vaultlocker service fails when some interface are DOWN with NO-CARRIER
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bionic Backports |
Fix Released
|
Undecided
|
James Page | ||
vaultlocker |
Fix Released
|
High
|
Unassigned | ||
vaultlocker (Ubuntu) |
Fix Released
|
High
|
James Page | ||
Disco |
Fix Released
|
High
|
James Page | ||
Eoan |
Fix Released
|
High
|
James Page |
Bug Description
[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-
[Original Bug Report]
On some hosts, it might be possible to have interfaces that are DOWN
with NO-CARRIER. In this case, systemd-
and fail. Therefore vaultlocker will also fail.
If vaultlocker fails it might impact the mount of the encrypted
partitions.
Changed in vaultlocker: | |
status: | New → Fix Released |
importance: | Undecided → High |
Changed in vaultlocker (Ubuntu Eoan): | |
assignee: | nobody → James Page (james-page) |
Changed in vaultlocker (Ubuntu Disco): | |
assignee: | nobody → James Page (james-page) |
Changed in vaultlocker (Ubuntu): | |
assignee: | nobody → James Page (james-page) |
status: | New → Triaged |
Changed in vaultlocker (Ubuntu Disco): | |
status: | New → Triaged |
Changed in vaultlocker (Ubuntu Eoan): | |
status: | New → Triaged |
Changed in vaultlocker (Ubuntu): | |
importance: | Undecided → High |
Changed in vaultlocker (Ubuntu Disco): | |
importance: | Undecided → High |
Changed in vaultlocker (Ubuntu Eoan): | |
importance: | Undecided → High |
Changed in vaultlocker (Ubuntu): | |
status: | Triaged → In Progress |
Changed in bionic-backports: | |
status: | New → In Progress |
assignee: | nobody → James Page (james-page) |
Changed in bionic-backports: | |
status: | In Progress → Fix Released |
https:/ /github. com/openstack- charmers/ vaultlocker/ pull/7 tries to address the issue by removing the dependency on systemd- networkd- wait-online.