[Bug 1839216] [NEW] xenial VM hangs copying block device
Public bug reported: With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the following script hangs in the dd command: == #!/bin/bash dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1 cp in.bin out.bin IN=$(losetup --show -f in.bin) OUT=$(losetup --show -f out.bin) typeset -i i=1 while true; do echo $i $(date) dd if=$IN of=$OUT bs=128k i=i+1 done == The trace (sorry, I don't have the exact kernel version... I found this mid-June 2019) looks like: # cat /proc/5230/stack [<0>] io_schedule+0x16/0x40 [<0>] wbt_wait+0x234/0x390 [<0>] blk_mq_make_request+0x103/0x590 [<0>] generic_make_request+0x122/0x2f0 [<0>] submit_bio+0x73/0x150 [<0>] submit_bh_wbc+0x17a/0x1b0 [<0>] __block_write_full_page+0x15b/0x400 [<0>] block_write_full_page+0x10c/0x130 [<0>] blkdev_writepage+0x18/0x20 [<0>] __writepage+0x1d/0x50 [<0>] write_cache_pages+0x228/0x4b0 [<0>] generic_writepages+0x5c/0x90 [<0>] blkdev_writepages+0x2f/0x40 [<0>] do_writepages+0x1f/0x70 [<0>] __filemap_fdatawrite_range+0xc6/0x100 [<0>] filemap_write_and_wait+0x31/0x90 [<0>] __blkdev_put+0x7a/0x210 [<0>] blkdev_put+0x4c/0xd0 [<0>] blkdev_close+0x34/0x70 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9a/0xc0 [<0>] exit_to_usermode_loop+0xce/0xd0 [<0>] do_syscall_64+0x116/0x150 [<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [<0>] 0x If we have used strace on the process, we find that dd is inside "close(1)" as it closes the output file. I don't know if this would reproduce on actual hardware, as I don't have a machine that large to play with. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839216 Title: xenial VM hangs copying block device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090593] Re: D.ROOT-SERVERS.NET changing January 3rd 2013
Precise reached EOL some time ago. Marking this "won't fix" ** Changed in: bind9 (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090593 Title: D.ROOT-SERVERS.NET changing January 3rd 2013 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload
** Changed in: maas/1.9 Assignee: LaMont Jones (lamont) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553176 Title: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683911] [NEW] ifup places illegally named variables into the environment
Public bug reported: When dhclient brings up interface eth0.55, the environment passed to scripts includes: IFUPDOWN_eth0=parent-lock IFUPDOWN_eth0.55=post-up IFACE=eth0.55 LOGICAL=eth0.55 ADDRFAM=inet METHOD=dhcp MODE=start PHASE=post-up VERBOSITY=0 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin IFUPDOWN_eth0.55 is not a valid name for an environment variable. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683911 Title: ifup places illegally named variables into the environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1683911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
This bug causes maas testing to fail (at least the ntp test, because of overlayfs and apparmor and ntp having a profile.) See https://bugs.launchpad.net/maas/+bug/1677336 Hardware testing is a requirement for MAAS 2.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408106 Title: attach_disconnected not sufficient for overlayfs To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408106 Title: attach_disconnected not sufficient for overlayfs To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673253] Re: "Screen Display" icon is missing from System Settings
I can confirm that downgrading from 15.04.0+17.04.20170314-0ubuntu1 to 15.04.0+17.04.20170213-0ubuntu1 makes the Display Icon return. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673253 Title: "Screen Display" icon is missing from System Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673253] [NEW] "Screen Display" icon is missing from System Settings
Public bug reported: After shoving in a new Nvidia GeForce 8400GS (and trying the proprietary drivers out), the Screen Display icon is completely missing from the Systems Settings on my machine. I'd kinda like it back. :/ Please let me know what other info you may need. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 14:35:38 2017 InstallationDate: Installed on 2014-09-22 (905 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673253 Title: "Screen Display" icon is missing from System Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse
Also true when TERM=screen -- I suspect it doesn't care what terminal you're using, if it can grab mouse events, it does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661691 Title: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1661691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse
A very unexpected, and totally unwelcome change to vim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661691 Title: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1661691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning
** Changed in: maas/2.1 Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640147 Title: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning
** Also affects: maas/2.1 Importance: Undecided Status: New ** Changed in: maas/2.1 Milestone: None => 2.1.4 ** Changed in: maas/2.1 Assignee: (unassigned) => LaMont Jones (lamont) ** Changed in: maas Assignee: (unassigned) => LaMont Jones (lamont) ** Changed in: maas Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640147 Title: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning
The loop of output is caused by maas trying to get an ipv6 address in a loop, even though the interface clearly does not support ipv6. (If it did, there would be a link-local address.) ** Changed in: isc-dhcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640147 Title: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning
tl;dr: dhclient -6 should be less spam-chatty in the presence of no ipv6 support. If dhclient logged that as one message, instead of 9 messages, then syslog would compress the output. The easiest way that I've seen to reproduce this is to boot with ipv6.disable=true on the kernel command line. Nobuto: do you have ipv6 disabled via the kernel command line? (This is known to cause various issues for a number of daemons.) ** Also affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640147 Title: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
** Also affects: maas/2.1 Importance: Undecided Status: New ** Tags added: maas-ipv6 ** Changed in: maas/2.1 Milestone: None => 2.1.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
Confirmed freeipmi-tools on xenial and yakkety. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload
Verified trusty using the same test as found in http://paste.ubuntu.com/23921176/ ** Tags removed: verification-needed ** Tags added: verification-done ** Changed in: bind9 (Ubuntu Trusty) Milestone: None => trusty-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553176 Title: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload
** Description changed: Since 2.6, linux has supported nanosecond granular time in stat(2) returns. BIND has a comment in the code that it might use it, but continues to ignore it. As of 9.9.3b2, named checks the time of (at least) zone files on disk (expanding to include include files in 9.10.0a2). Because the check is only done to a granularity of seconds, changing the zone file twice in the same second can cause BIND to decide that it need not reload the zone, even though it is out of date. [Impact] - * If a zone file is changed (generally by automated processes) more + * If a zone file is changed (generally by automated processes) more than once in a second, bind9 happily thinks it has already loaded the zone. A trivial demonstration of the bug can be seen at - paste.ubuntu.com/23921121/ + paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the + same test with the fixed code. Making this a test case is somewhat + problematic in that it needs to make sure that they happen inside of the + same second. - * MAAS is exactly the sort of use case that hits this bug. + * MAAS is exactly the sort of use case that hits this bug. - * The upload changes BIND's utility function to actual use the + * The upload changes BIND's utility function to actual use the st_mtim.tv_nsec instead of '0'. [Test Case] - * See the pastebin above. (Change a zone file and reload it, and then + * See the pastebin above. (Change a zone file and reload it, and then do it again less than a second later.) [Regression Potential] - * Ignoring the whole "rebuilds sometimes break things", the most likely + * Ignoring the whole "rebuilds sometimes break things", the most likely regression would be one where something was either relying on BIND not reloading the dozone (unlikely), or otherwise relying on the modify time on a zone file to some arbitrary value. [Other Info] - This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March + This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March 2016. ** Also affects: bind9 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: bind9 (Ubuntu Xenial) Status: New => 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/1553176 Title: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload
** Description changed: Since 2.6, linux has supported nanosecond granular time in stat(2) returns. BIND has a comment in the code that it might use it, but continues to ignore it. As of 9.9.3b2, named checks the time of (at least) zone files on disk (expanding to include include files in 9.10.0a2). Because the check is only done to a granularity of seconds, changing the zone file twice in the same second can cause BIND to decide that it need not reload the zone, even though it is out of date. + + [Impact] + + * If a zone file is changed (generally by automated processes) more + than once in a second, bind9 happily thinks it has already loaded the + zone. A trivial demonstration of the bug can be seen at + paste.ubuntu.com/23921121/ + + * MAAS is exactly the sort of use case that hits this bug. + + * The upload changes BIND's utility function to actual use the + st_mtim.tv_nsec instead of '0'. + + [Test Case] + + * See the pastebin above. (Change a zone file and reload it, and then + do it again less than a second later.) + + [Regression Potential] + + * Ignoring the whole "rebuilds sometimes break things", the most likely + regression would be one where something was either relying on BIND not + reloading the dozone (unlikely), or otherwise relying on the modify time + on a zone file to some arbitrary value. + + [Other Info] + + This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March + 2016. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553176 Title: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
Package verified in zesty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
** Changed in: freeipmi (Ubuntu) Milestone: None => ubuntu-17.04 ** Also affects: freeipmi (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: freeipmi (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: maas Milestone: None => 2.2.0 ** Description changed: See also https://github.com/chu11/freeipmi-mirror/issues/8 and https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs to successfully discover the ipv6 address of a hosts BMC. [Impact] - * Machines with BMCs configured to use IPv6 addresses, ipmi-config -(silently) fails to show those values. + * Machines with BMCs configured to use IPv6 addresses, ipmi-config + (silently) fails to show those values. - * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config -finding the IPv6 address of the BMC. + * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config + finding the IPv6 address of the BMC. - * This upload is a backport of an upstream work-in-progress to add IPv6 -configuration parameters to ipmi-config. While the eventual upstream -source may differ slightly as the branch lands, this delivers the -information for use. ANYONE USING THIS CODE NEEDS TO BE PREPARED TO -CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS. + * This upload is a backport of an upstream work-in-progress to add IPv6 + configuration parameters to ipmi-config. While the eventual upstream + source may differ slightly as the branch lands, this delivers the + information for use. ANYONE USING THIS CODE NEEDS TO BE PREPARED TO + CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS. [Test Case] - * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6 -address configured on the iLO. Try to get ipmi-config to give you -that address. + * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6 + address configured on the iLO. Try to get ipmi-config to give you + that address. - * This upload introduces the Lan6_Conf section (which may change when -1.6 finally arrives.) The following displays the IPv6 Addresses of -the BMC: - ipmi-config --checkout --category=core --section=Lan6_Conf + * This upload introduces the Lan6_Conf section (which may change when + 1.6 finally arrives.) The following displays the IPv6 Addresses of + the BMC: + ipmi-config --checkout --category=core --section=Lan6_Conf [Regression Potential] - * Scripting that uses --checkout and no section/key-pair specification -will now see the additional Lan6_Conf section, which has the potential -to confuse said script. + * Scripting that uses --checkout and no section/key-pair specification + will now see the additional Lan6_Conf section, which has the potential + to confuse said script. - * If upstream changes the presentation of the data, anyone who has -adopted this pre-release of same may see differences. The section is -clearly marked as subject to change in 1.6, and missing in 1.5. (If -Ubuntu syncs 1.5, MAAS is committed to porting this change forward. -Upstream has committed to the feature being present in 1.6.) + * If upstream changes the presentation of the data, anyone who has + adopted this pre-release of same may see differences. The section is + clearly marked as subject to change in 1.6, and missing in 1.5. (If + Ubuntu syncs 1.5, MAAS is committed to porting this change forward. + Upstream has committed to the feature being present in 1.6.) [Other Info] + + Once the changes are available, MAAS will need to change to use the new + Lan6_Conf section. ** Changed in: freeipmi (Ubuntu Xenial) Milestone: None => xenial-updates ** Changed in: freeipmi (Ubuntu Yakkety) Milestone: None => yakkety-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
** Description changed: See also https://github.com/chu11/freeipmi-mirror/issues/8 and https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs to successfully discover the ipv6 address of a hosts BMC. + + [Impact] + + * Machines with BMCs configured to use IPv6 addresses, ipmi-config +(silently) fails to show those values. + + * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config +finding the IPv6 address of the BMC. + + * This upload is a backport of an upstream work-in-progress to add IPv6 +configuration parameters to ipmi-config. While the eventual upstream +source may differ slightly as the branch lands, this delivers the +information for use. ANYONE USING THIS CODE NEEDS TO BE PREPARED TO +CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS. + + [Test Case] + + * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6 +address configured on the iLO. Try to get ipmi-config to give you +that address. + + * This upload introduces the Lan6_Conf section (which may change when +1.6 finally arrives.) The following displays the IPv6 Addresses of +the BMC: + ipmi-config --checkout --category=core --section=Lan6_Conf + + [Regression Potential] + + * Scripting that uses --checkout and no section/key-pair specification +will now see the additional Lan6_Conf section, which has the potential +to confuse said script. + + * If upstream changes the presentation of the data, anyone who has +adopted this pre-release of same may see differences. The section is +clearly marked as subject to change in 1.6, and missing in 1.5. (If +Ubuntu syncs 1.5, MAAS is committed to porting this change forward. +Upstream has committed to the feature being present in 1.6.) + + [Other Info] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
** Summary changed: - freeipmi ipmi-config (and discovery) lacks ipv6 support + freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters ** Description changed: - See also https://github.com/chu11/freeipmi-mirror/issues/8 -- freeipmi - needs to successfully discover the ipv6 address of a hosts BMC. + See also https://github.com/chu11/freeipmi-mirror/issues/8 and + https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs to + successfully discover the ipv6 address of a hosts BMC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658750] Re: fails to add search directive to resolv.conf
Note that while there is no DOMAINSEARCH, DNSDOMAIN needs to translate into something (domain or search directive), and only one of those will be honored by the resolver (they overwrite each other, per the specification). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658750 Title: fails to add search directive to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658750] [NEW] fails to add search directive to resolv.conf
Public bug reported: When open-iscsi creates /etc/resolv.conf, it fails to add the domain name to resolv.conf: See also http://askubuntu.com/questions/873701/maas-node-unable-to- resolve-its-own-hostname/874005 ubuntu@resolve:~$ cat /run/net-ens3.conf DEVICE='ens3' PROTO='dhcp' IPV4ADDR='172.18.145.5' IPV4BROADCAST='172.18.147.255' IPV4NETMASK='255.255.252.0' IPV4GATEWAY='172.18.144.1' IPV4DNS0='192.168.133.18' IPV4DNS1='0.0.0.0' HOSTNAME='' DNSDOMAIN='maas.example.com' NISDOMAIN='' ROOTSERVER='172.18.144.1' ROOTPATH='' filename='pxelinux.0' UPTIME='8' DHCPLEASETIME='600' DOMAINSEARCH='' ubuntu@resolve:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.133.18 ubuntu@resolve:~$ dpkg -l open-iscsi | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3.3 amd64iSCSI initiator tools ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658750 Title: fails to add search directive to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655049] Re: [2.1] netaddr raises IndexError when looking up some OUI registrations
The actual source of the issue seems to be that netaddr indexes a file that it doesn't own (from ieee-data package), and then assumes that it won't change underneath it (either because of an ieee-data update, or a netaddr update in the case of a running process), which results in various exceptions and other errors from the code. I believe that a fresh bug is being filed against python-netaddr on the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655049 Title: [2.1] netaddr raises IndexError when looking up some OUI registrations To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1655049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655049] Re: [2.1] netaddr raises IndexError when looking up some OUI registrations
Interesting point. Here is what I see:
[xenial]
ii ieee-data 20150531.1 all OUI and IAB listings
ii python3-netaddr 0.7.18-1 all manipulation of various common
netwo
% python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import netaddr
>>> netaddr.EUI('00:22:59:11:22:33').oui.registration().org
'Guangzhou New Postcom Equipment Co.,Ltd.'
[zesty]
ii ieee-data 20160613.1all OUI and IAB listings
ii python3-netaddr 0.7.18-2 all manipulation of various
common network
% python3
Python 3.5.2+ (default, Dec 13 2016, 14:16:35)
[GCC 6.2.1 20161212] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import netaddr
>>> netaddr.EUI('00:22:59:11:22:33').oui.registration().org
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/netaddr/eui/__init__.py", line 478, in
oui
return OUI(self.value >> 24)
File "/usr/lib/python3/dist-packages/netaddr/eui/__init__.py", line 98, in
__init__
self._parse_data(data, offset, size)
File "/usr/lib/python3/dist-packages/netaddr/eui/__init__.py", line 145, in
_parse_data
record['org'] = line.split(None, 2)[2]
IndexError: list index out of range
>>>
That is netaddr is not sufficiently hardened against the newer ieee-
data. While it's conceivable that the actual bug is in ieee-data, it
would seem that hardening the code to better deal with it would be good.
The entry that breaks reads:
00-22-59 (hex)Guangzhou New Postcom Equipment Co.,Ltd.
002259 (base 16)Guangzhou New Postcom Equipment Co.,Ltd.
No.3¡¡Guangpuxi Road,Guangzhou Science
City,
Guangzhou Guangdong 510663
CN
while the same entry in the working file is:
00-22-59 (hex) Guangzhou New Postcom Equipment Co.,Ltd.
002259 (base 16) Guangzhou New Postcom Equipment Co.,Ltd.
No.3¡¡Guangpuxi Road,Guangzhou Science
City,
Guangzhou Guangdong 510663
CHINA
(Note the leading pair of spaces...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655049
Title:
[2.1] netaddr raises IndexError when looking up some OUI registrations
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1655049/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628761] Re: [2.1] netaddr assumes MAC OUI is ascii
Likewise, as of 0.7.18-2, the mac prefixes 00:22:59, 00:23:89, and 5c:15:15 generate IndexError, because unicode is treated as ascii. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628761 Title: [2.1] netaddr assumes MAC OUI is ascii To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1628761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655049] Re: List index out of range on main page and nodes page
MAAS was incomplete in the workaround for Bug#1628761. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655049 Title: List index out of range on main page and nodes page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1655049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655049] Re: List index out of range on main page and nodes page
I found some that exhibit the issue (00-22-59, 00-23-89) for starters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655049 Title: List index out of range on main page and nodes page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1655049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655049] Re: List index out of range on main page and nodes page
Can you provide the first 3 octets of one of the bad MACs? If you're not sure which one, the following is sure to catch it: sudo maas-region dbshell select distinct substring(cast(mac_address as varchar) for 8) from maasserver_interface; This would appear to be a bug in the python3-netaddr, which MAAS should probably armor itself against. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655049 Title: List index out of range on main page and nodes page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1655049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1
There is a new test version in the ppa. This one built. :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654453 Title: LMTP delivery to Dovecot stops working in 3.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1
@mamarley - A postfix package with the fix (for testing) is in ppa:lamont/postfix -- can you confirm that the bug is fixed with that version? thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654453 Title: LMTP delivery to Dovecot stops working in 3.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1
3.1.4-3 should be uploaded this weekend, with the fix. ** Changed in: postfix (Ubuntu) Status: Confirmed => Fix Committed ** Bug watch added: Debian Bug tracker #850430 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850430 ** Also affects: postfix (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850430 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654453 Title: LMTP delivery to Dovecot stops working in 3.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1
On Sat, Jan 07, 2017 at 01:26:41PM -, Michael Marley wrote: > I just upgraded and still have exactly the same problem as before. During the upgrade, did it say that it was changing master.cf as below? In master.cf: using smtp binary for lmtp service (symlink removed) In either case, please send me unredacted (other than any passwords) master.cf and /var/log/apt/term.log from the upgrade? lamont -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654453 Title: LMTP delivery to Dovecot stops working in 3.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1
Based on the reported contents of the line, I'm assuming that's the case and uploading 3.1.4-2. If that doesn't fix it, please reopen this bug. ** Changed in: postfix (Ubuntu) Importance: Undecided => Critical ** Changed in: postfix (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: postfix (Ubuntu) Assignee: (unassigned) => LaMont Jones (lamont) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654453 Title: LMTP delivery to Dovecot stops working in 3.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1
Is it possible that there is trailing whitespace on the lmtp line in master.cf? That would explain the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654453 Title: LMTP delivery to Dovecot stops working in 3.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking
And leaving it triaged for MAAS, since once initramfs-tools supports it, MAAS will need to propagate that to the UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632808 Title: Consider supporting IPv6 autoconf in configure_networking To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632480] Re: Latest Yakkety grub timesout when attempting to UEFI boot over IPv6
I am not able to reproduce this. Is this still an issue for the machine in question? ** Changed in: grub2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632480 Title: Latest Yakkety grub timesout when attempting to UEFI boot over IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking
I am also not aware of anyone in the MAAS space who _wants_ autoconf for ipv6 networks. I am aware of at least one who wants it OFF for their networks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632808 Title: Consider supporting IPv6 autoconf in configure_networking To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632808] Re: configure_networking exits without any ipv6 routes
Converting this to be the bug for ip6=stateless (or ip6=autoconf?), as the rest of it was solved with 1621507. ** Changed in: maas Status: New => Fix Released ** Summary changed: - configure_networking exits without any ipv6 routes + Consider supporting IPv6 autoconf in configure_networking ** Changed in: maas Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632808 Title: Consider supporting IPv6 autoconf in configure_networking To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
No maas changes were required here, since it always specifies both ip= and ip6= ** Changed in: maas Status: New => 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/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618543] Re: freeipmi lacks IPv6 support
No maas changes were needed here. ** Changed in: maas Status: Triaged => 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/1618543 Title: freeipmi lacks IPv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229458] Re: grubnetx64.efi tftp client does not work over ipv6
Verified that both IPv4 pxeboot and IPv6 uefi boot cleanly into MAAS. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229458 Title: grubnetx64.efi tftp client does not work over ipv6 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1229458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] Re: freeipmi ipmi-config (and discovery) lacks ipv6 support
** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config (and discovery) lacks ipv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
Verification was done by using MAAS to enlist, commission, and deploy xenial (with the fix) on a machine. Previously, it failed to shut down, because the root disk got unmounted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init
Discussed in IRC, all of the test cases in question have been met. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621615 Title: network not configured when ipv6 netbooted into cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Reconfirmed yakkety today.
Also tested "ip6= without ip=": which yakkety currently hates, but we've
decided to handle separately after this SRU lands, partially because
it's a trivial workaround ("for ipv6-only, specify "ip6=dhcp ip=off")
and also not a case that anything needing the SRU actually does. (MAAS
always specifies both, with one of them set to "off".)
Marking this verification-done.
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
Bugs related to uploads for this specific SRU:
cloud-init:
bug 1460715: different fix unrelated to this SRU
bug 1639930: ip6= on kernel command line
bug 1642679: different fix unrelated to this SRU
bug 1644043: different fix unrelated to this SRU
ifupdown:
bug 1629972: networking.service takes down lo on stop
initramfs-tools:
bug 1621507: no IPv6 DHCP support in early boot
bug 1628306: regression-update (failure when ip="")
bug 1631474: regression-update (failure when ip=:eth0:dhcp)
isc-dhcp:
bug 1621507: no IPv6 DHCP support in early boot
bug 1633479: dhclient does not wait for IPv6 DAD
open-iscsi:
bug 1621507: no IPv6 DHCP support in early boot
[Impact]
It is not possible to netboot Ubuntu with a network-based root
filesystem in an ipv6-only environment. Anyone wanting to netboot in an
ipv6-only environment is affected.
[Stable Fix]
These uploads add "ip6=" to the command line syntax to configure ipv6
using the defacto isc-dhcp-client. IPv4 configuration (and "ip="
syntax) remain unchanged.
Valid format for the ip6= command line option is:
ip6=none (or ip6=off or ip6=) -- do not configure ipv6
ip6=DEVICE -- run IPv6 dhclient on device DEVICE.
[Test Case]
See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only
netbooting world. Pass the boot process an ipv6 address to talk to, and
see it fail to configure the network.
[Regression Potential]
1) This increases the uncompressed initramfs size by approximately 500KB,
since isc-dhcp-client is added, but klibc is still needed for some other
things, and is therefore present. On systems with a very small /boot
partition, this could result in failure to upgrade the initramfs.
2) In at least some cases, DHCP network configuration shifts from klibc's
ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as
isc-dhcp-client is in very very widespread use. In the event of a regression,
network boot would fail, but the prior kernel should still be bootable.
[Tests for verification]
Whoever checks the last one off, please mark verification done.
MAAS test cases:
X / Y
- [+]/[ ] MAAS on IPv6-only network
- [+]/[ ] MAAS on IPv4-only network
- [+]/[ ] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
- [+]/[ ] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
+ [+]/[+] MAAS on IPv6-only network
+ [+]/[+] MAAS on IPv4-only network
+ [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
+ [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
Non-MAAS test cases:
X / Y
[+]/[+] ip="" and ip6 not present
[+]/[+] ip=:eth0:dhcp and ip6 not present
[+]/[+] d-i install with iSCSI remote root should complete normally
[+]/[+] Validate normal boot without remote root
[+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
[+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
[+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
[+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of
booting device)52-54-00-53-5d-24
[+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4
should be used only)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools configure_networking() fails to dhcp ipv6 addresses
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650631] Re: ip6=dhcp turns on ip=dhcp
Based on a conversation with Scott, we are both of the opinion that this bug should not delay the landing of the fixes for bug 1621507 and bug 1621615 into xenial and yakkety. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650631 Title: ip6=dhcp turns on ip=dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1650631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: X / Y - [+]/[+] MAAS on IPv6-only network - [+]/[+] MAAS on IPv4-only network - [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6) - [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4) + [+]/[ ] MAAS on IPv6-only network + [+]/[ ] MAAS on IPv4-only network + [+]/[ ] MAAS booting IPv4 on dual-stack network (with and without dhcp6) + [+]/[ ] MAAS booting IPv6 on dual-stack network (with and without dhcp4) Non-MAAS test cases: X / Y [+]/[+] ip="" and ip6 not present [+]/[+] ip=:eth0:dhcp and ip6 not present [+]/[+] d-i install with iSCSI remote root should complete normally [+]/[+] Validate normal boot without remote root [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=) [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=) [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)52-54-00-53-5d-24 [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Final review feedback has been incorporated into initramfs-tools, isc- dhcp, and open-iscsi, and uploaded to zesty. ** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: - [+] MAAS on IPv6-only network - [+] MAAS on IPv4-only network - [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6) - [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4) + X / Y + [+]/[+] MAAS on IPv6-only network + [+]/[+] MAAS on IPv4-only network + [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6) + [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4) Non-MAAS test cases: - X/Y + X / Y [+]/[ ] ip="" and ip6 not present [+]/[ ] ip=:eth0:dhcp and ip6 not present [+]/[ ] d-i install with iSCSI remote root should complete normally [+]/[ ] Validate normal boot without remote root [+]/[ ] Booting an iSCSI remote root via IPv4 (using ip=) [+]/[ ] Booting an iSCSI remote root via IPv6 (using ip6=) [+]/[ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [+]/[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device) [+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: [+] MAAS on IPv6-only network [+] MAAS on IPv4-only network - [+] MAAS booting IPv4 on dual-stack network - [+] MAAS booting IPv6 on dual-stack network + [+] MAAS booting IPv4 on dual-stack network (with and without dhcp6) + [+] MAAS booting IPv6 on dual-stack network (with and without dhcp4) Non-MAAS test cases: + [ ] ip="" and ip6 not present + [ ] ip=:eth0:dhcp and ip6 not present [ ] d-i install with iSCSI remote root should complete normally [+] Validate normal boot without remote root [ ] Booting an iSCSI remote root via IPv4 (using ip=) [ ] Booting an iSCSI remote root via IPv6 (using ip6=) [ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [ ] Booting an iSCSI remote root via IPv6 (no ip6=, d-i use case) [ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device) [ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Today, I tested all of the MAAS cases with current -proposed from both xenial and yakkety. Behaves as expected. ** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: [+] MAAS on IPv6-only network [+] MAAS on IPv4-only network - [ ] MAAS booting IPv4 on dual-stack network - [ ] MAAS booting IPv6 on dual-stack network + [+] MAAS booting IPv4 on dual-stack network + [+] MAAS booting IPv6 on dual-stack network Non-MAAS test cases: [ ] d-i install with iSCSI remote root should complete normally [ ] Validate normal boot without remote root [ ] Booting an iSCSI remote root via IPv4 (using ip=) [ ] Booting an iSCSI remote root via IPv6 (using ip6=) [ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [ ] Booting an iSCSI remote root via IPv6 (no ip6=, d-i use case) [ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device) [ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) [ ] jderose's use cases ** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Marking the "normal boot, no remote root" as verified, since I did that about a dozen times today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: - [ ] MAAS on IPv6-only network - [ ] MAAS on IPv4-only network + [+] MAAS on IPv6-only network + [+] MAAS on IPv4-only network [ ] MAAS booting IPv4 on dual-stack network [ ] MAAS booting IPv6 on dual-stack network Non-MAAS test cases: [ ] d-i install with iSCSI remote root should complete normally [ ] Validate normal boot without remote root [ ] Booting an iSCSI remote root via IPv4 (using ip=) [ ] Booting an iSCSI remote root via IPv6 (using ip6=) [ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [ ] Booting an iSCSI remote root via IPv6 (no ip6=, d-i use case) [ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device) [ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) [ ] jderose's use cases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
One way to reproduce this issue (and the workaround): 1) Install and configure MAAS, with DHCP on at least one subnet on the rack 2) purge maas-rack-controller: this will remove /var/lib/maas/dhcpd.conf 3) reinstall maas-rack-controllerL: this will start the rack controller, but not recreate /var/lib/maas/dhcpd.conf Note the lack of a dhcpd, due to no config file. 4) use the CLI to disable dhcp (example is fabric 0, untagged vlan): maas SESSION vlan 0 0 dhcp_on=False 5) use the CLI to enable dhcp (same fabric/vlan as #4): maas SESSION vlan 0 0 dhcp_on=True Note that we now have a working dhcpd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot - [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. + + [Tests for verification] + + Whoever checks the last one off, please mark verification done. + + MAAS test cases: + [ ] MAAS on IPv6-only network + [ ] MAAS on IPv4-only network + [ ] MAAS booting IPv4 on dual-stack network + [ ] MAAS booting IPv6 on dual-stack network + + Non-MAAS test cases: + [ ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Merge proposal linked: https://code.launchpad.net/~lamont/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/312899 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565060] Re: defaults file is ignored
** Changed in: bind9 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565060 Title: defaults file is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1565060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init - * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) - + * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. - These uploads address this by replacing the one-off klibc dhcp client - (IPv4-only) with the defacto standard isc-dhcp-client, and thereby - provide both ipv6 and ipv4 DHCP configuration. + These uploads add "ip6=" to the command line syntax to configure ipv6 + using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" + syntax) remain unchanged. + + Valid format for the ip6= command line option is: +ip6=none (or ip6=off or ip6=) -- do not configure ipv6 +ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647586] [NEW] apparmor errors with current ntp
Public bug reported: On ntpd restart, this gets logged. (1:4.2.8p8+dfsg-1ubuntu2) Dec 6 01:14:05 rover3 kernel: [16526.813113] audit: type=1400 audit(1481012045.534:136): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=29435 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=123 ouid=0 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647586 Title: apparmor errors with current ntp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1647586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618543] Re: freeipmi lacks IPv6 support
Verified. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618543 Title: freeipmi lacks IPv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618543] Re: freeipmi lacks IPv6 support
** Description changed: - 1.4.11 lacks any ipv6 support. 1.5.3 (current upstream from 1 Aug 2016) - also lacks ipv6 support. + ipmipower in 1.4.11 and 1.5 lack ipv6 support. This is in-plan for 1.6 + from upstream. - Note that both ipmitool (since 2014 or so) and openipmi (since - 2003-11-11) support IPv6. + The -h argument to ipmipower needs to be extended to accept + [ip:v6::addr]:port type syntax, and the processing of the hostnames + needs to take into account ipv6 addresses as well. + + [Impact] + + * If a BMC has only IPv6 addresses, then ipmipower cannot discover it. + + * MAAS needs to be able to do just that. + + [Test Case] + + * To reproduce / verify the bug, configure a BMC with an IPv6 address, and +try to talk to it. + + [Regression Potential] + + * If a BMC has both IPv6 and IPv4 addresses in the DNS, and the hostname +is used to control it, then this change will cause ipmipower to try +IPv6 first, where it used to completely ignore IPv6 in the DNS. We +believe this to be the correct behavior and that it does not affect +the current installed base. (IPv6 BMC addresses are not a thing that +we have been able to find anywhere.) ** Description changed: ipmipower in 1.4.11 and 1.5 lack ipv6 support. This is in-plan for 1.6 from upstream. + + See also related bug 1645912. The -h argument to ipmipower needs to be extended to accept [ip:v6::addr]:port type syntax, and the processing of the hostnames needs to take into account ipv6 addresses as well. [Impact] - * If a BMC has only IPv6 addresses, then ipmipower cannot discover it. + * If a BMC has only IPv6 addresses, then ipmipower cannot discover it. - * MAAS needs to be able to do just that. + * MAAS needs to be able to do just that. [Test Case] - * To reproduce / verify the bug, configure a BMC with an IPv6 address, and -try to talk to it. + * To reproduce / verify the bug, configure a BMC with an IPv6 address, and + try to talk to it. [Regression Potential] - * If a BMC has both IPv6 and IPv4 addresses in the DNS, and the hostname -is used to control it, then this change will cause ipmipower to try -IPv6 first, where it used to completely ignore IPv6 in the DNS. We -believe this to be the correct behavior and that it does not affect -the current installed base. (IPv6 BMC addresses are not a thing that -we have been able to find anywhere.) + * If a BMC has both IPv6 and IPv4 addresses in the DNS, and the hostname + is used to control it, then this change will cause ipmipower to try + IPv6 first, where it used to completely ignore IPv6 in the DNS. We + believe this to be the correct behavior and that it does not affect + the current installed base. (IPv6 BMC addresses are not a thing that + we have been able to find anywhere.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618543 Title: freeipmi lacks IPv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645912] [NEW] freeipmi ipmi-config (and discovery) lacks ipv6 support
Public bug reported: See also https://github.com/chu11/freeipmi-mirror/issues/8 -- freeipmi needs to successfully discover the ipv6 address of a hosts BMC. ** Affects: freeipmi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645912 Title: freeipmi ipmi-config (and discovery) lacks ipv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1645912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618543] Re: freeipmi lacks IPv6 support
** Also affects: freeipmi (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618543 Title: freeipmi lacks IPv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618543] Re: freeipmi lacks IPv6 support
See also https://github.com/chu11/freeipmi-mirror/pull/7 -- IPv6 support is in-plan for freeipmi 1.6, and we'll be pulling various bits back into 1.4/1.5 for Ubuntu, starting with ipmipower getting support for IPv6. ** Also affects: freeipmi (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618543 Title: freeipmi lacks IPv6 support To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
open-iscsi is verified for xenial and yakkety ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229458] Re: grubnetx64.efi tftp client does not work over ipv6
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229458 Title: grubnetx64.efi tftp client does not work over ipv6 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1229458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
** Also affects: maas Importance: Undecided Status: New ** Tags added: maas-ipv6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632804] Re: ROUNDTTT in configure_networking is effectively ignored
*** This bug is a duplicate of bug 1621507 *** https://bugs.launchpad.net/bugs/1621507 ** This bug has been marked a duplicate of bug 1621507 initramfs-tools configure_networking() fails to dhcp ipv6 addresses -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632804 Title: ROUNDTTT in configure_networking is effectively ignored To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init
My currently-pending MPs address the issue and work in conjunction with the new fixes for Bug#1621507: https://code.launchpad.net/~lamont/cloud-init/+git/bug-1621615-device6/+merge/309718 https://code.launchpad.net/~lamont/cloud-initramfs-tools/bug-1621615-device6/+merge/309719 These need to land in zesty, and get SRUed to xenial and yakkety. ** Changed in: maas Status: Fix Released => In Progress ** Changed in: cloud-init Status: Fix Committed => Confirmed ** Changed in: cloud-init (Ubuntu) Status: Fix Released => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Released => Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu) Status: Fix Released => Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu Xenial) Status: Fix Released => Confirmed ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-initramfs-tools (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: maas Milestone: 2.1.0 => 2.1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621615 Title: network not configured when ipv6 netbooted into cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
all 3 debdiffs need to land in zesty, and be backported to yakkety and xenial for SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Patch added: "isc-dhcp debdiff" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770861/+files/isc-dhcp.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
attached debdiff needs to roll forward into zesty. ** Changed in: initramfs-tools (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
All of the debdiffs need to be rolled into zesty, and backported to yakkety, xenial. ** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => In Progress ** Changed in: isc-dhcp (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: isc-dhcp (Ubuntu Yakkety) Status: Fix Released => In Progress ** Changed in: open-iscsi (Ubuntu) Status: Fix Released => In Progress ** Changed in: open-iscsi (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: open-iscsi (Ubuntu Yakkety) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Patch added: "open-iscsi debdiff" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770860/+files/open-iscsi.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
I'm attaching debdiffs for initramfs-tools, isc-dhcp, and open-iscsi. The combination (along with cloud-initramfs-tools and cloud-init -- see bug 1621615) seem to work with maas in IPv4, IPv6, and dual stack (booting IPv4 and IPv6), when added to yakkety-proposed. ** Patch added: "debdiff for initramfs-tools" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770859/+files/initramfs-tools.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init
** Merge proposal linked: https://code.launchpad.net/~lamont/cloud-init/+git/bug-1621615-device6/+merge/309718 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621615 Title: network not configured when ipv6 netbooted into cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Changed in: maas Status: Fix Released => In Progress ** Changed in: maas Assignee: (unassigned) => LaMont Jones (lamont) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635654] Re: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion
After you change your /e/n/i to that, and reproduce the issue, break=init, and then mount -oremount,rw /root; chroot /root; vi /etc/network/interfaces and comment out everything from "auto br1" to end of file, exit; mount -oremount,ro /root; exit and you're back to a bootable system... Which is why the apport files are pretty much useless on this report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635654 Title: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635654] Re: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion
The reboot of the system prior to this morning was after a dist-upgrade on "2016-10-14 08:30:10" according to /var/log/apt/history.log -- the upgrade to zesty occurred on 2016-10-18, and the reboot was after a fresh dist-upgrade this morning, on zesty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635654 Title: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635654] [NEW] Machine fails to stop, or start interfaces. hangs in systemd waiting for completion
Public bug reported: The attached /etc/network/interfaces file is fatal to /lib/systemd/system/networking.service, resulting in a loop that never finishes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ifupdown 0.8.13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 21 09:14:33 2016 InstallationDate: Installed on 2014-09-22 (759 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: ifupdown UpgradeStatus: Upgraded to zesty on 2014-11-14 (706 days ago) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635654 Title: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635654] Re: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion
** Attachment added: "/e/n/i that results in a loop" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+attachment/4764881/+files/interfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635654 Title: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
After more discussion, marking this verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
I have confirmed that this functions as expected for MAAS (behaves exactly like 0.122ubuntu8.1 did.) Not marking verification-done, but +1 from me/MAAS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
0.122ubuntu8.4 still fails to get an IP when the switchport is not 'portfast' (and the switch therefore passes no traffic for 60 seconds after link-up.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Filed the above 2 issues as (1) Bug #1632804 and (2) Bug #1632808 for yakkety. noting that here because those should be fixed as part of the xenial SRU of this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632804] Re: ROUNDTTT in configure_networking is effectively ignored
** Also affects: maas Importance: Undecided Status: New ** Tags added: maas-ipv6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632804 Title: ROUNDTTT in configure_networking is effectively ignored To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632808] [NEW] configure_networking exits without any ipv6 routes
Public bug reported: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router-advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. ** Affects: maas Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: maas-ipv6 ** Tags added: maas-ipv6 ** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632808 Title: configure_networking exits without any ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632804] [NEW] ROUNDTTT in configure_networking is effectively ignored
Public bug reported:
With the changes from Bug #1621507, ROUNDTTT is effectively ignored.
The loop checks only for the existence of /run/net-${DEVICE}.conf, and
the dhclient scripts ALWAYS (even on failure) create it, it will try to
get a lease exactly once before bailing out. Ideally, if both ipv4 and
ipv6 are present on the vlan, then both would be configured and (as is
done) present in the net-$DEV.conf file. Generally speaking (and why we
didn't notice this in testing..), dhclient gets a lease on the first
pass.
** Affects: maas
Importance: Undecided
Status: New
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: maas-ipv6
** Package changed: klibc (Ubuntu) => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632804
Title:
ROUNDTTT in configure_networking is effectively ignored
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632804/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
After looking into this more (and working on Bug #1629972 some), there
are couple of issues with the new configure_networking:
1. since it checks only for the existence of /run/net-${DEVICE}.conf,
and the dhclient scripts ALWAYS (even on failure) create it, it will try
to get a lease exactly once before bailing out. Ideally, if both ipv4
and ipv6 are present on the vlan, then both would be configured and (as
is done) present in the net-$DEV.conf file.
2. Since router-advertisements are needed for the on-link indication
(and routes), ipv6 configuration via dhcp should wait until such time as
there is at least a (non-fe80) route for some ipv6 cidr on $DEVICE
(which RA should create). This will eliminate the iscsi-timeout errors
that we see when configure_networking() returns before RA configures
routing. Note that a default route is not necessary. Note also that it
should timeout on the RA if it doesn't show up in a reasonable time,
complain that it got no RA, and then _not_ bring up ipv6 on the
interface (RA is required, as per Bug #1609898)
** Tags removed: verification-pending
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools configure_networking() fails to dhcp ipv6 addresses
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
ifupdown is actually behaving correctly in this case. It's likely that cloud-initramfs-tools should be marking the interface "iface foo inet[6] manual" in every case, since that's the indicator that seems to prevent ifdown from downing the interface. When I had it do that, what I then found was that we had gotten to "reached shutdown target", and the system was then having timeouts in systemd watchdogs. Looking at it with systemd's debug shell, /media /root-ro (the iscsi volume) has been unmounted, and /media/root-rw (the overlayfs) is still mounted. Interestingly, the last few things are: [ OK ] Unmounted /media/root-rw. [ OK ] Reached target Unmount All Filesystems. [ OK ] Stopped target Local File Systems (Pre). Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [ OK ] Stopped Remount Root and Kernel File Systems [ OK ] Stopped Create Static Device Nodes in /dev. [ OK ] Reached target Shutdown 5 seconds later is the "connection 1:0: ping timeout of 5 secs expired, and / is still (or is that "again") mounted on overlayfs rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw//overlay,workdir=/media/root-rw//overlay-workdir And then there is the collection of "INFO: task systemd:1 blocked for more than 120 seconds." log entries on the console. ** Changed in: ifupdown (Ubuntu) Assignee: LaMont Jones (lamont) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Tags removed: verification-done ** Tags added: verification-pending -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632096] Re: dhclient-script does not respect ip6_prefixlen
*** This bug is a duplicate of bug 1609898 *** https://bugs.launchpad.net/bugs/1609898 The DHCP v6 protocol does not include prefixlen: On-link indication comes from router-advertisements, only. So it's not so much that the script is ignoring it, as it is that dhclient is making up answers. ** This bug has been marked a duplicate of bug 1609898 dhclient incorrectly assumes a /64 ipv6 prefix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632096 Title: dhclient-script does not respect ip6_prefixlen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1632096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
This was resolved by switching away from klibc's ipconfig ** Changed in: klibc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
This was resolved by switching away from klibc's ipconfig ** Changed in: klibc (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631010] [NEW] please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot
Public bug reported: Right now, I can boot with "ip=hostname:BOOTIF" in the kernel commandline, and (after bug 1621507), I get whatever it came up with for ipv4 and ipv6. If for nothing more than testing on a dual-stack environment, it would be nice to be able to force that to try both (current behavior, and an excellent default), only try IPv4, or only IPv6. NOT something that needs to be fixed before yakkety, but would be nice to eventually get back to xenial. ** Affects: initramfs-tools (Ubuntu) Importance: Wishlist Status: New ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631010 Title: please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init
The packages have been verified in xenial-proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621615 Title: network not configured when ipv6 netbooted into cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
