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/1694801
Title:
sysconfig needs fix for ipv6 gateway routes
Status in cloud-init:
Fix Released
Bug description:
Static IPV6 subnet with a ipv6 route fails to set the default IPV6
gateway.
With cloud-init master:
% cat ipv6-static.yaml
network:
version: 1
config:
- type: physical
name: interface0
mac_address: "52:54:00:12:34:00"
subnets:
- type: static
address: 2001:4800:78ff:1b:be76:4eff:fe06:96b3
netmask: 'ffff:ffff:ffff:ffff::'
routes:
- gateway: 2001:4800:78ff:1b::1
netmask: '::'
network: '::'
% ./tools/net-convert.py --network-data ipv6-static.yaml \
--kind yaml --output-kind sysconfig -d target-sysconfig
% grep -nr IPV6_DEFAULTGW target-sysconfig/; echo $?
1
Currently only the subnet is checked for 'ipv6' setting, however, the routes
array may include a mix of v4 or v6 configurations, in particular, the gateway
in a route may be ipv6, and if so, should export the value via IPV6_DEFAULTGW
in the ifcfg-XXXX file.
Additionally, if the route is v6, it should rendering a routes6-XXXX
file; this is present but missing the 'dev <interface>' scoping.
% cat target-sysconfig/etc/sysconfig/network-scripts/route6-interface0
# Created by cloud-init on instance boot automatically, do not edit.
#
::/0 via 2001:4800:78ff:1b::1
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1694801/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
