yahoo-eng-team team mailing list archive

[shixuantong <2015528@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Refer to the following code:

https://github.com/canonical/cloud-
init/blob/e71f0a13d84d69e1342f822702e13ddbd904aca0/cloudinit/net/__init__.py#L534

https://github.com/canonical/cloud-
init/blob/e71f0a13d84d69e1342f822702e13ddbd904aca0/cloudinit/net/__init__.py#L537

If the current nic already has a bond, should the bond instead of the
nic be returned? If the nic is returned, the same IP address may be set
for both bond and the original nic during setting ephemeral network，and
may some unknown errors occur.

** Affects: cloud-init
     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/2015528

Title:
  Obtaining why the NIC Skips the Bond or Bridge

Status in cloud-init:
  New

Bug description:
  Refer to the following code:

  https://github.com/canonical/cloud-
  init/blob/e71f0a13d84d69e1342f822702e13ddbd904aca0/cloudinit/net/__init__.py#L534

  https://github.com/canonical/cloud-
  init/blob/e71f0a13d84d69e1342f822702e13ddbd904aca0/cloudinit/net/__init__.py#L537

  If the current nic already has a bond, should the bond instead of the
  nic be returned? If the nic is returned, the same IP address may be
  set for both bond and the original nic during setting ephemeral
  network，and may some unknown errors occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2015528/+subscriptions