yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #62805
[Bug 1677846] [NEW] Unable to configure IPv4 addresses via network configuration injected into config drive
Public bug reported:
When I attempt to use cloud-init 0.7.9 with RHEL72, I am finding that
IPv4 network configuration information is not properly configured on the
eth0 interface. Instead, I end up with an ifcfg-eth0 that looks like
this:
[root@projectb-fwam-rhel72 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=fa:16:3e:54:5a:77
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
cloud-init.log indicates that network_data.json is being used for the
network configuration information (although the network_config content
file is available as well).
The config drive is attached.
** Affects: cloud-init
Importance: Undecided
Status: New
** Attachment added: "config-drive.iso"
https://bugs.launchpad.net/bugs/1677846/+attachment/4850849/+files/config-drive.iso
--
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/1677846
Title:
Unable to configure IPv4 addresses via network configuration injected
into config drive
Status in cloud-init:
New
Bug description:
When I attempt to use cloud-init 0.7.9 with RHEL72, I am finding that
IPv4 network configuration information is not properly configured on
the eth0 interface. Instead, I end up with an ifcfg-eth0 that looks
like this:
[root@projectb-fwam-rhel72 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=fa:16:3e:54:5a:77
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
cloud-init.log indicates that network_data.json is being used for the
network configuration information (although the network_config content
file is available as well).
The config drive is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1677846/+subscriptions