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/1685532
Title:
Unit tests for sysconfig are flawed:
Status in cloud-init:
Fix Released
Bug description:
Unit tests for sysconfig are flawed:
E.g.:
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=static
DEVICE=eth0
IPV6ADDR=2607:f0d0:1002:0011::2
IPV6INIT=yes
NETMASK=64
NM_CONTROLLED=no
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
'''
Compare this to the doc:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html
IPV6ADDR=address
where address is the first static, or primary, IPv6 address on an
interface.
The format is Address/Prefix-length. If no prefix length is specified,
/64 is assumed. Note that this setting depends on IPV6INIT being enabled.
NETMASK is a parameter for ipv4.
NETMASKn=mask
where mask is the netmask value and the n is expected to be consecutive
positive integers starting from 0 (for example, NETMASK0). It is used for
configurations with multiple IP addresses on an interface. It can be omitted if
there is only one address being configured.
The tests are also incomplete, lacking several scenarios.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1685532/+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
