[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164 ** Bug watch added: Debian Bug tracker #851164 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1642903 Title: introduce disk/by-id (model_serial)

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

Pull request for trusty: https://code.launchpad.net/~ddstreet/+git/systemd/+ref/trusty Pull request for xenial: https://code.launchpad.net/~ddstreet/+git/systemd/+ref/xenial Yakkety can use the same patches as Xenial. Zesty can use the same patches as upstream (from github, listed in comment

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

for NetworkManager, this is fixed starting in wily (see comment 13) and so should work in xenial/yakkety; and in trusty, dhclient still works (per description stating dhclient works in isc-dhcp-client 4.2.4-7ubuntu14). I'm not sure if NetworkManager using dhcpv6 works in precise (but who is using

[Touch-packages] [Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

I verified that the -proposed package does create the NVMe disk/by-id/ serial number symlink for each drive. However, there's unfortunately a bug in the way it does it, which still exists upstream. I opened this upstream udev bug for the problem: https://github.com/systemd/systemd/issues/4833

[Touch-packages] [Bug 1647485] [NEW] NVMe symlinks broken by devices with spaces in model or serial strings

Public bug reported: [Impact] After including the patch from bug 1642903, NVMe devices that include spaces in their model or serial strings result in incorrect symlinks, e.g. if the model string is "XYZ Corp NVMe drive" then instead of creating: /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

** Tags added: sts sts-sponsor sts-sru -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1647485 Title: NVMe symlinks broken by devices with spaces in model or serial

[Touch-packages] [Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

I opened bug 1647485 to track the spaces-in-symlink-value problem. Separate from that bug, I have verified the -proposed udev package creates the /dev/disk/by-id/ model/serial string symlinks. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

patch filename and Subject: had 'string_escape=release', fixed to 'string_escape=replace'. Actual patch contents were correct and aren't changed in this patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

** Patch removed: "workaround-use-string_escape-release-for-nvme-symlin.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4790906/+files/workaround-use-string_escape-release-for-nvme-symlin.patch ** Patch added:

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

Note: the workaround patch from comment 17 *will not* conflict with whatever fix is implemented upstream. The patch changes *only* the NVMe rules to force whitespace replacement. If upstream changes the default behavior, to replace whitespace, then this workaround patch becomes

[Touch-packages] [Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

** Description changed: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number.

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

** Description changed: [Impact] After including the patch from bug 1642903, NVMe devices that include spaces in their model or serial strings result in incorrect symlinks, e.g. if the model string is "XYZ Corp NVMe drive" then instead of creating: /dev/disk/by-id/nvme-XYZ Corp NVMe

[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

Scott, while this is a linux-specific change (and not applicable to upstream isc-dhcp itself), it doesn't look like this fix is upstream in debian; have you opened a bug there and/or are you planning to push it up? -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

Marking this as 'invalid' for ifupdown, as the problem is in the vlan package's script. ** Also affects: vlan (Ubuntu) Importance: Undecided Status: New ** Changed in: vlan (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: vlan (Ubuntu) Importa

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

Thanks everyone, I'll work on getting the patch upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

** Patch added: "lp1573272-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850617/+files/lp1573272-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

** Description changed: - Expectation: After reboot, route for default gateway specified on - bonded interface is installed according to "gateway x.x.x.x" (where - x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or - files sourced per /etc/network/interfaces + [Impact] +

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

I created a PPA with fixed vlan packages: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1573272 ** Tags removed: bot-comment patch xenial ** Tags added: sts-sponsor ** Tags added: patch ** Also affects: vlan (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

** Patch added: "lp1573272-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850619/+files/lp1573272-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

** Patch added: "lp1573272-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850620/+files/lp1573272-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu.

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

** Patch added: "lp1573272-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850618/+files/lp1573272-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 ** Bug watch added: Debian Bug tracker #859127 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

ifup $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribe

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

I set up a default xenial vm with 2 extra interfaces, and configured them with exactly the config you listed in the description, and left it in a reboot loop checking for the default gateway each time, and it hasn't seen the problem at all, after hours of rebooting. Is there a something else

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

Ok I've reproduced this by introducing a delay by changing /lib/systemd/system/ifup@.service -ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \ +ExecStart=/bin/sh -ec '/usr/bin/test %I == bond0 && echo found bond0 && sleep 3 ; ifup --allow=hotplug %I; ifup --allow=auto %I;

[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind

*** This bug is a duplicate of bug 1447715 *** https://bugs.launchpad.net/bugs/1447715 This was fixed via update to isc-dhcp in bug 1633479. Please see that bug for the specific isc-dhcp version number needed to fix the bug. ** This bug has been marked a duplicate of bug 1447715 dhclient

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

updated debdiff to remove trailing whitespace which 'quilt refresh' complained about, and convert the patch header to DEP-3 format. ** Patch removed: "lp1689854-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+attachment/4874866/+files/lp1689854-trusty.debdiff

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1689854 Title: Multiple DHCPv6 client interfaces fail to receive some server responses

[Touch-packages] [Bug 1689854] [NEW] Multiple DHCPv6 client interfaces fail to receive some server responses

is included in Xenial and later releases. This patch is needed only in the Trusty release. ** Affects: isc-dhcp (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Changed in: isc-dhcp (Ubuntu) Importance: Undecided => Medium ** Changed in:

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

Fixed by upstream isc-dhcp commit 4b8251a0c06b7d8706a28904fdef2414f045cc2c ('Fix the socket handling for DHCPv6 clients to allow multiple instances of a clinet on a single machine to work properly.') -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

** Patch added: "lp1689854-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+attachment/4874777/+files/lp1689854-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

I reproduced the problem with: ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.8 amd64common files used by all the isc-dhcp* packages After adding

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

updated debdiff, to correct patch file line offsets to match trusty codebase ** Patch removed: "lp1689854-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+attachment/4874777/+files/lp1689854-trusty.debdiff ** Patch added: "lp1689854-trusty.debdiff"

[Touch-packages] [Bug 1693819] [NEW] dhclient DHCPv6 does not work with interface alias

Public bug reported: [Impact] The isc-dhcp-client dhclient program does not work with interface alias names, e.g. eth0:1. It fails immediately. [Test Case] On trusty through artful, find an interface that is connected to a network that has a DHCPv6 server on it. First verify it can get a

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

This problem is because isc-dhcp strips the interface alias when it enumerates the system interfaces, i.e. in common/discover.c function next_iface(): /* interface aliases look like "eth0:1" or "wlan1:3" */ s = strchr(info->name, ':');

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

Test packages available in this PPA https://launchpad.net/~ddstreet/+archive/ubuntu/lp1693819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1693819 Title: dhclient

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

This is specifically important for any configuration that wants to have both a IPv4 address and DHCPv6 IPv6 address on a single interface, and uses ifupdown for interface management, and wants independent control of the 4 and 6 address. Meaning, to be able to add or remove an interface's IPv6

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Changed in: isc-dhcp (Ubuntu Zesty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: isc-dhcp (Ubuntu Yakkety) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: isc-dhcp (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884175/+files/lp1693819-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884176/+files/lp1693819-artful.debdiff ** Changed in: isc-dhcp (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: isc

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884173/+files/lp1693819-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884172/+files/lp1693819-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884174/+files/lp1693819-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

This has been assigned upstream ISC bug: ISC-Bugs #45294 ISC's bug tracking is not public, so there is no way to track any upstream progress in fixing this. ** Bug watch added: Debian Bug tracker #863426 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863426 ** Also affects: isc-dhcp

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

PPA updated with the current patches. https://launchpad.net/~ddstreet/+archive/ubuntu/lp1693819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1693819 Title: dhclient

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819v2-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4891684/+files/lp1693819v2-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819v2-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4891682/+files/lp1693819v2-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819v2-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4891685/+files/lp1693819v2-artful.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

Attached patches that rework the patch, instead of changing common/discover.c to strip the interface alias during name comparison, the new patch strips the interface alias in client/dhclient.c before copying the argv parameter, so dhclient does not use the alias at all. I tested in t/x/y/z/a and

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch removed: "lp1693819-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884172/+files/lp1693819-trusty.debdiff ** Patch removed: "lp1693819-xenial.debdiff"

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

** Patch added: "lp1693819v2-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4891683/+files/lp1693819v2-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

The attached debdiffs introduce a regression, please hold off applying until I can investigate and update the patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

I should note: 1. The isc-dhcp code is common between dhcpd and dhclient 2. The current system interfaces are enumerated in common/discover.c, and that code - in next_iface() - strips the interface alias from all enumerated interfaces, so when dhcpd or dhclient is comparing a parameter against

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

opened upstream merge request 6814: https://github.com/systemd/systemd/pull/6814 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714505 Title: systemd kmod builtin uses

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

> Changed in systemd: > status: New → Fix Released for clarification, this is not Fix Released upstream, it has been rejected as Won't Fix upstream, systemd/udev believes it isn't their problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

> Here is a sample patch against debian-installer-utils to try. yes i think it at least needs to go here, to handle this very specific case. It may be better to put it into the if $TRIGGER section, as I don't think it is needed for only the settle case, but either way should work. This was

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

Also, this upstream udev bug has caused trouble before, e.g.: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1549456 that does a udev reload too, but only when specific devices are found. Hopefully this change to update-dev will cover more cases where this upstream udev bug will cause

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

this applies only to trusty; initramfs-tools in later releases is fixed already. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1718055 Title: update-initramfs

[Touch-packages] [Bug 1718055] [NEW] update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu) As

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

** Patch added: "lp1718055-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+attachment/4953633/+files/lp1718055-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

@xnox, the person that reported this to me and who can reproduce it, tested with a initrd including your update-dev patch and it does fix the problem. Can you go ahead and merge it and SRU please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

Note this is fixed in upstream debian by commit: commit 3cb744c9cf39f0dc178370ef6235a1b30f8c7d06 Author: Ben Hutchings Date: Tue Dec 8 02:53:23 2015 + hook-functions: Rewrite block device sysfs lookup to be generic That commit is a larger change that reworks

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

the linux autopkgtest failure is due to the kernel team change to only build a single kernel 'flavour' to reduce test rebuild time, but the autopkgtest still expects the (no longer built) -lpae flavor on armhf. The kernel team has a bug open for it and is fixing it in the next build. -- You

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

As trusty can use the 4.4 kernel (via lts-xenial), this needs backporting to trusty initramfs-tools also, please. ** Patch added: "lp1712491-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1712491/+attachment/4961737/+files/lp1712491-trusty.debdiff -- You

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

** Changed in: initramfs-tools (Ubuntu Trusty) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

the linux-lts-xenial autopkgtest failures are due to that pkg's test expecting the running kernel == test kernel, which is wrong as trusty is running stock 3.13 linux in the test, and the linux-lts autopkgtest doesn't upgrade to linux-lts-* kernel. so unrelated to this change. e.g.

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

** Changed in: ifupdown (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: i

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

> networking.service spawns ifup@.services in parallel with no ordering information no, networking.service calls ifup -a, it doesn't spawn ifup@ services. ifup -a doesn't bring up interfaces in parallel, it brings them up sequentially as ordered in the /etc/networking/interface file(s). However,

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

** Changed in: isc-dhcp (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: isc-dhcp (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: isc-dhcp (Ubuntu Zesty) Assignee: (unassigned) => Dan Streetman

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

** Patch added: "lp1718568-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/4968659/+files/lp1718568-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

** Patch added: "lp1718568-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/4968657/+files/lp1718568-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

** Patch added: "lp1718568-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/4968656/+files/lp1718568-artful.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

** Patch added: "lp1718568-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/4968658/+files/lp1718568-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

Hi Jeff, Thanks for reporting and debugging this! I've tweaked your patch from comment 2 slightly, you can see my version in the debdiffs attached. I was concerned that just a " " check may not always work right, so I explicitly check for the ip output to contain 'inet6' (but not 'tentative')

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

** Changed in: isc-dhcp (Ubuntu Bb-series) Status: New => In Progress ** Changed in: isc-dhcp (Ubuntu Bb-series) Importance: Undecided => Medium ** Changed in: isc-dhcp (Ubuntu Bb-series) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug not

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

only now started seeing the problem after upgrading to the latest vlan package. Can you open a new bug for your issue please? ** Changed in: ifupdown (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubu

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

ubuntu@lp1712491:~$ dpkg -l | grep initramfs-tools ii initramfs-tools0.103ubuntu4.8 all tools for generating an initramfs ii initramfs-tools-bin0.103ubuntu4.8 amd64binaries used by

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

failing autopkg tests for this: linux-lts-xenial (and other EOL linux-lts-*) these failures are due to bug 1723223; known bug that is not related to this bug. linux-exynos5 on armhf this failed due to a testbed failure, unrelated to this bug. linux on armhf this failure is due to bug

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

** Changed in: systemd (Ubuntu Zesty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) *

[Touch-packages] [Bug 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device

$ dpkg -l | grep initramfs-tools ii initramfs-tools 0.103ubuntu4.7 all tools for generating an initramfs ii initramfs-tools-bin 0.103ubuntu4.7 amd64binaries used by initramfs-tools $ sudo

[Touch-packages] [Bug 1714505] [NEW] systemd kmod builtin uses out of date kmod context

oken operation. [Other Info] This needs fixing upstream, which I'm in progress on. ** Affects: systemd (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

** Also affects: systemd via https://github.com/systemd/systemd/issues/6723 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

https://github.com/systemd/systemd/issues/6723 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714505 Title: systemd kmod builtin uses out of date kmod context Status in

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

note that the test script in the description must be run as root on a system that does have a nvme drive that isn't in use (because the nvme module can't be removed if any nvme drive is in use). ** Bug watch added: github.com/systemd/systemd/issues #6723

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

slight update to test script, add a check to make sure the nvme module was unloaded - if any nvme partitions are mounted it would cause a false positive result. #!/bin/bash MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host modprobe -rq nvme mv $MOD_DIR/nvme.ko . depmod -a sleep 3

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

grr, please note line wrap in above comment; script should be: #!/bin/bash MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host modprobe -rq nvme mv $MOD_DIR/nvme.ko . depmod -a sleep 3 udevadm trigger sleep 1 mv nvme.ko $MOD_DIR/ depmod -a grep -q nvme /proc/partitions \ && echo FAIL

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

yep, having up to 3 seconds worth of stale system data is too much time. Also, I think the builtins can just validate themselves - for example the kmod builtin can trivially call kmod_validate_resource(ctx) every time it's asked to load a module, and I think the other builtins that implement

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

: Medium Assignee: Dan Streetman (ddstreet) Status: Won't Fix ** Changed in: debian-installer-utils (Ubuntu Artful) Status: New => Fix Released ** Changed in: debian-installer-utils (Ubuntu Zesty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: debian-ins

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

> I would feel better if a wider call-for-testing could be done on these > packages > in bionic-proposed yes i agree; the mailing lists that comes to mind is ubuntu-server, do you have any other ML suggestion? -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

I updated the ifupdown pkg builds in my test ppa using the upstream (debian) patch, which is a variation of my previous patch. Anyone affected by this regression please test with the latest ifupdown and vlan pkgs from my ppa. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

I sent an email to ubuntu-server list requesting anyone with vlan ifupdwon config to give these -proposed pkgs a test. I'll also perform verification for them when I have a chance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

> could we get the SRU template information included in this bug? doh. sorry, been awfully busy lately. added. ** Description changed: + [impact] + + in bug 1573272, the vlan pkg was changed to perform a full ifup inside + its if-pre-up.d/vlan script. This allowed correct ordering of ifup

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

** Changed in: ifupdown (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

trusty: root@lp1701023:~# dpkg -l | grep ifupdown ii ifupdown 0.7.47.2ubuntu4.4 amd64high level tools to configure network interfaces root@lp1701023:~# dpkg -l | grep vlan ii vlan 1.9-3ubuntu10.5

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

xenial: root@lp1701023-x:/etc/network/interfaces.d# dpkg -l |grep ifupdown ii ifupdown 0.8.10ubuntu1.4 amd64high level tools to configure network interfaces root@lp1701023-x:/etc/network/interfaces.d# dpkg -l |grep vlan ii vlan

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

tested bionic per comment 19 with: root@lp1701023-b:~# dpkg -l | grep ifupdown ii ifupdown 0.8.17ubuntu1 amd64 high level tools to configure network interfaces root@lp1701023-b:~# dpkg -l | grep vlan ii vlan

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

tested on artful with: root@lp1701023-a:~# dpkg -l | grep ifupdown ii ifupdown 0.8.16ubuntu2.1 amd64high level tools to configure network interfaces root@lp1701023-a:~# dpkg -l | grep vlan ii vlan

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

@newsuk-platform, are you still having this problem? If not, let's close this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: ifup -a does not start

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

> Unfortunately it turns out this change does not fix the issue of interfaces > not > coming up correctly for a bond with a (static) network configuration Please keep in mind this bug is *specifically* about the regression caused by the change from bug 1573272, as described in this bug

<    1   2   3   4   5   6   7   8   9   10   >