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
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:
** 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 l
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
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
** 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
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:
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
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
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
** 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
** 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
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
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.
** 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.
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
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
** 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
** 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
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
** 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,
** 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
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
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'
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
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
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:
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
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
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,
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
@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.
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
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,
mitted
** 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 i
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
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
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.
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.
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
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:
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
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
** 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
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.
** 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
** 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
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:
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
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.
** 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
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:
** 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
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:
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
** 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
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
** 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
** 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
** 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
** 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
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"
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
** 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
-
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
** 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
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:
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
** 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
** 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
*** 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,
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
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
** 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
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:
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)
** 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.
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
** 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
** 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
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
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
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
** 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.
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
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.
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.
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.
** 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
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
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
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
dia/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 receive
** 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
*** 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 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:
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:
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
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
1 - 100 of 1183 matches
Mail list logo
