@mfo thanks yeah, the piece of info that was missing for me is that the
interfaces need to be down AND have a netplan configuration in order for
the issue to trigger which in my repro was not the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** 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/1838607
Title:
vaultlocker service fails when some interface are DOWN with NO
Hi Ed,
I looked into this, and the issue only happens if such interfaces (with
state DOWN and NO-CARRIER) are managed by systemd-networkd (check with
'networkctl list').
Per systemd-networkd-wait-online.service man page [1]:
'By default, it will wait for all links it is aware of and which are
ma
I'm trying to understand why I do not see this issue. I have several
interfaces DOWN and vaultlocker does not have this issue on boot:
root@chespin:~# ip a s| grep ": eno"
2: eno1: mtu 1500 qdisc mq state DOWN group
default qlen 1000
3: eno2: mtu 1500 qdisc mq state DOWN group
default qlen 100
Validation for Bionic from James Page PPA.
I created a bionic VM, configured vault on another machine and installed
vaultlocker from the repo.
Used vaultlocker to encrypt a partition:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE
MOUNTPOINT
sda
I've uploaded a backport of 1.0.4-0ubuntu0.19.04.1 to the bionic-
backports queue for backports team review
--
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 whe
This bug was fixed in the package vaultlocker - 1.0.4-0ubuntu0.19.04.1
---
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: #18
This bug was fixed in the package vaultlocker - 1.0.4-0ubuntu0.19.10.1
---
vaultlocker (1.0.4-0ubuntu0.19.10.1) eoan; 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: #183
Validation for eoan.
I created an eoan VM, configured vault on another machine and installed
vaultlocker from the repo.
Used vaultlocker to encrypt a partition:
lsblk
lsblk
NAME MAJ:MIN RM SIZE RO TYPE
MOUNTPOINT
loop0
James, Brian,
Now that it has been tested and validated that the change works for Disco and
Eoan, I guess that we'll have to wait 7 more days to have it in
{disco,eoan}-proposed.
What about Bionic? Is it possible to backport it?
--
You received this bug notification because you are a member of
Validation for disco.
I created a disco VM, configured vault on another machine and installed
vaultlocker from the repo.
Used vaultlocker to encrypt a partition:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE
MOUNTPOINT
loop0
Hello Nicolas, or anyone else affected,
Accepted vaultlocker into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/vaultlocker/1.0.4-0ubuntu0.19.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
This bug was fixed in the package vaultlocker - 1.0.4-0ubuntu1
---
vaultlocker (1.0.4-0ubuntu1) focal; urgency=medium
* New upstream release (LP: #1838607):
- d/p/*: Drop all patches, included in release.
-- James Page Thu, 05 Dec 2019 14:49:04 +
** Changed in: vaultloc
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 mana
** Also affects: bionic-backports
Importance: Undecided
Status: New
** Changed in: bionic-backports
Status: New => In Progress
** Changed in: bionic-backports
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member o
** Changed in: vaultlocker (Ubuntu Eoan)
Assignee: (unassigned) => James Page (james-page)
** Changed in: vaultlocker (Ubuntu Disco)
Assignee: (unassigned) => James Page (james-page)
** Changed in: vaultlocker (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed i
Could we please backport it and make it available to Bionic?
I faced that again for another customer deployment.
--
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 fail
** Changed in: vaultlocker
Status: New => Fix Released
** Changed in: vaultlocker
Importance: Undecided => High
** Also affects: vaultlocker (Ubuntu)
Importance: Undecided
Status: New
** Also affects: vaultlocker (Ubuntu Eoan)
Importance: Undecided
Status: New
** A
18 matches
Mail list logo