yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67947
[Bug 1669504] Re: net/sysconfig.py is broken with ipv4 + ipv6 interfaces
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1669504
Title:
net/sysconfig.py is broken with ipv4 + ipv6 interfaces
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in cloud-init source package in Yakkety:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
This code path is not applicable to Ubuntu.
The bug was in supporting dual stack network configuration in
sysconfig (Redhat/centos) format.
[Test Case]
Launch an instance on lxd, make sure it has network.
[Regression Potential]
Changes to network rendering could have negatively affected Ubuntu
the test above is valid to check that that didn't go horribly wrong.
[Other Info]
Upstream commit:
https://git.launchpad.net/cloud-init/commit/?id=1d751a6f46
=== End SRU Template ===
Given a network configuration that includes ipv4 and ipv6 configuration for an interface, as in:
"networks": [
{
"id": "public-ipv6",
"ip_address": "2604:A880:0400:00D0:0000:0000:1714:F001/64",
"link": "interface-public",
"netmask": "",
"neutron_network_id": "937c94de-7029-586e-6e36-ea9af2d815de",
"type": "ipv6",
"routes": [
{
"gateway": "2604:A880:0400:00D0:0000:0000:0000:0001",
"netmask": "::",
"network": "::"
}
]
},
{
"id": "public-ipv4",
"ip_address": "198.199.75.198",
"link": "interface-public",
"netmask": "255.255.255.0",
"neutron_network_id": "7d9cd798-2dc0-502f-41ca-e04b552ddffd",
"type": "ipv4",
"routes": [
{
"gateway": "198.199.75.1",
"netmask": "0.0.0.0",
"network": "0.0.0.0"
}
]
}
]
cloud-init will fail because both subnets provide a default route,
resulting in the error:
Duplicate declaration of default route found for interface eth0
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1669504/+subscriptions
References