Public bug reported:
Create VM on Microsoft Azure with size Standard_A8_v2 with 1 NIC.
After VM is running, shutdown VM.
Attach 7 NICs.
Start VM.
In some rate, some nics not get the IP, /sys/class/net/eth7/operstate is down.
I saw the log in cloud-init, when it reads file /sys/class/net/eth7/operstate.
If this file is written by kernel, then it is not a cloud-init issue, but
kernel issue?
** Affects: cloud-init
Importance: Undecided
Status: New
** Attachment added: "ubuntu-bug cloud-init"
https://bugs.launchpad.net/bugs/1852162/+attachment/5304646/+files/apport.cloud-init.6_t0cxww.apport
--
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/1852162
Title:
Some NIC didn't get the IP when attach multiple nics after VM
provisioned on azure
Status in cloud-init:
New
Bug description:
Create VM on Microsoft Azure with size Standard_A8_v2 with 1 NIC.
After VM is running, shutdown VM.
Attach 7 NICs.
Start VM.
In some rate, some nics not get the IP, /sys/class/net/eth7/operstate is
down.
I saw the log in cloud-init, when it reads file
/sys/class/net/eth7/operstate. If this file is written by kernel, then it is
not a cloud-init issue, but kernel issue?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1852162/+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
