please reopen if this is still an issue
** Changed in: systemd (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/1732002
Title:
cloud images in lxc get ipv6
This bug was fixed in the package nplan - 0.32~17.10.4
---
nplan (0.32~17.10.4) artful; urgency=medium
* bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
* debian/postinst: Write breadcrumbs on
This bug was fixed in the package nplan - 0.32~16.04.5
---
nplan (0.32~16.04.5) xenial; urgency=medium
* bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
* Do not attempt to rebind driver
Verification-done on artful: nplan 0.32~17.10.4
As above for the xenial tests: I get an IPv6 address when I should, and
no IPv6 address when I shouldn't, based on the setup of the LXD bridge.
Behavior is as expected.
** Tags removed: verification-needed verification-needed-artful
Verification-done on xenial: nplan 0.32~16.04.5
nplan-configured LXD container appears to behave as expected: on a setup
with IPv6 enabled, I get an IPv6 address on the container without a
startup delay. In a host with IPv6 disabled on the lxd bridge, the
container also starts up appropriately,
Hello Scott, or anyone else affected,
Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.5 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Scott, or anyone else affected,
Accepted nplan into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.4 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+ All users of netplan.
+
+ [Test case]
+
+ == LXD containers ==
+ 1) Start an LXD container (artful or bionic)
+ 2) Verify that an IPv6 address is present
+ 3) Verify that the system is brought up in a reasonable time (does not wait 2
minutes to be
This got landed in netplan.io 0.35 in bionic. The changes still should
be part of a SRU.
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The MP has been moved to a github PR:
https://github.com/CanonicalLtd/netplan/pull/19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732002
Title:
cloud images in lxc get ipv6 address
To manage
** Merge proposal linked:
https://code.launchpad.net/~raharper/netplan/+git/netplan/+merge/342976
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732002
Title:
cloud images in lxc get ipv6
Guys, I'm no longer suggesting that we disable RA here. After our
discussion I updated this bug
to indicate that we really want some way to *leave* RA alone.
At this point that means netplan needs to *NOT* emit AcceptRA values
into the .network configuration
files by default (as it does now),
I'd like to +1 what cyphermox said, the expected behavior on Ubuntu is
that if you do receive a RA, you let the kernel configure it.
That's how Ubuntu has been ever since IPv6 support was enabled and I
personally have about 200 systems that very much rely on this (no
specific IPv6 configuration,
The kernel value is equivalent to not writing it out, yes; I thought
it'd be better to be explicit in the config.
W.r.t disabling by default; no plans to do so at this point but as it is
now, all Artful and Bionic images will block for 10 seconds, unless an
RA comes in sooner. So ideally we stop
What's the point of having 'kernel'? You have a boolean here
specifically because you'll likely want to override the default,
whatever it might be. I'm fine with *not writing* accept-ra if that
helps, but for most cases, this is just the kind of option that people
should avoid touching.
FWIW, as
It would be nice for both nplan and networkd to accept a tri-state:
accept-ra: [off|on|kernel]
I think that would make it clear rather than an unset value to indicate
that it's controlled by the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After some discussion, it appears that networkd is kinda of making a
boolean (on|off) for IPV6 RA, when it's really a tri-state
(on|off|kernel).
Upstream networkd indicates there is a tri-state; like so:
Enable or disable IPv6 Router Advertisement (RA) reception support for
the interface. Takes
I've got a branch which would have cloud-init disable accept-ra unless
cloud-init has an explicit ipv6 configuration (static or dhcp6). This
only affects the solicitation effort, ipv6 link-local is of course,
unaffected as is explicit ipv6 configuration. I believe LXD is in a
position to know if
Yeah, i guess it is, given steps to reproduce are all in one go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732002
Title:
cloud images in lxc get ipv6 address
To manage notifications about
I can't remember if the host kernel also has changed defaults, thus host
kernel might be a spanner in the works too. All of the above was tested
on the same host kernel, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wonder if cloud images need to ship an extra netplan snippet to
disable ipv6 addresses by default, of if netplan default need changing,
or kernel default needs changing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
21 matches
Mail list logo
