yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81067
[Bug 1857031] [NEW] cloud-init configures wrong interface when trying to configure two interfaces with OpenStack cloud
Public bug reported:
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.
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)
** Affects: cloud-init
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/bugs/1857031/+attachment/5314061/+files/cloud-init.tar.gz
** Also affects: nova
Importance: Undecided
Status: New
--
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 configures wrong interface when trying to configure two
interfaces with OpenStack cloud
Status in cloud-init:
New
Status in OpenStack Compute (nova):
New
Bug description:
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.
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
Follow ups