Public bug reported:
Using Ubuntu 16.04.1 ppc64le and cloud-init
0.7.7~bzr1256-0ubuntu1~16.04.1 and deploying via Openstack Newton using
ConfigDrive datasource.
Initial boot of the vm applies the static networking correctly from the
config drive, however, if the config drive is removed and the vm is
rebooted, the static network info that was applied on initial boot is
wiped and replaced with fallback DHCP network.
Attaching logs from original boot and then second boot ( where the
networking is wrong ).
** Affects: cloud-init
Importance: Undecided
Status: New
** Attachment added: "Logs"
https://bugs.launchpad.net/bugs/1661679/+attachment/4812609/+files/logs.tar
--
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/1661679
Title:
Removing ConfigDrive causes network info to fallback to DHCP on reboot
Status in cloud-init:
New
Bug description:
Using Ubuntu 16.04.1 ppc64le and cloud-init
0.7.7~bzr1256-0ubuntu1~16.04.1 and deploying via Openstack Newton
using ConfigDrive datasource.
Initial boot of the vm applies the static networking correctly from
the config drive, however, if the config drive is removed and the vm
is rebooted, the static network info that was applied on initial boot
is wiped and replaced with fallback DHCP network.
Attaching logs from original boot and then second boot ( where the
networking is wrong ).
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1661679/+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
