Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3523
** Bug watch added: github.com/canonical/cloud-init/issues #3523 https://github.com/canonical/cloud-init/issues/3523 ** Changed in: cloud-init Status: Incomplete => Expired -- 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/1857031 Title: cloud-init fails to configure network interfaces running with OpenStack cloud Status in cloud-init: Expired Status in OpenStack Compute (nova): Invalid Bug description: cloud-init 18.5: Node has 3 interfaces: -enp5s0f0 - not connected -enp5s0f1 - connected -ib0 - an HFI port Centos7.6 running on the node. Openstack boots the server with two interfaces enp5s0f1 and ib0 and it is successful but the node is not reachable. On the node, the cloud- init configures the wrong interface enp5s0f0. It is because cloud-init fails to configure network interfaces running with OpenStack cloud if any of the network interfaces don't exist on the node. In this case, ib0 was missing. Please note that when I try to boot the server with only 1 interface enp5s0f1, everything works fine and the node is reachable too. Logs: http://paste.openstack.org/show/787707/ network-data and nics: http://paste.openstack.org/show/787797/ (note that enp5s0f1 is manually configured) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1857031/+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
