Project

General

Profile

Actions

Bug #10888

closed

duplicate interfaces when using bond device

Added by Sven Vogel over 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Network
Target version:
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hi,

when we create a bond device with kickstart we get duplicate interfaces. we thinks its not correct handling of bond and the same mac addresses.

normally the bond master and slaves have the same mac. it there a fix in the future?

thanks

Sven


Files

error.png View error.png 31.8 KB Sven Vogel, 06/20/2015 09:08 AM

Related issues 3 (0 open3 closed)

Related to Foreman - Bug #10546: Reduce the number of interfaces duplicatesDuplicate05/19/2015Actions
Related to Foreman - Bug #10805: VLAN interface attached to bond is wrongly created as BondClosedMarek Hulán06/13/2015Actions
Related to Foreman - Bug #10607: bonding on ubuntu causes foreman to create an interface after each ubuntu server rebootClosedMarek Hulán05/26/2015Actions
Actions #1

Updated by Sven Vogel over 8 years ago

macaddress_bond0 => 00:19:99:cb:c2:e2

macaddress_enp8s0f0 => 00:19:99:9e:41:08

macaddress_enp8s0f1 => 00:19:99:9e:41:09

macaddress_ens5f0 => 00:19:99:99:16:1a

macaddress_ens5f1 => 00:19:99:99:16:1b

macaddress_ens5f2 => 00:19:99:99:16:1c

macaddress_ens5f3 => 00:19:99:99:16:1d

macaddress_ens7f0 => 00:19:99:CB:C2:E2

macaddress_ens7f1 => 00:19:99:CB:C2:E3

puppet will do it correct but foreman should seperate the bond0 from it slaves,

Actions #2

Updated by Marek Hulán over 8 years ago

Could you please upload full output of facter? Feel free to remove sensitive information, I'm mostly interested in interfaces and mac_* facts. Are all of interfaces (except bond) physical or do you use vlans/aliases? It might be related to #10805 and #10546

Actions #3

Updated by Marek Hulán over 8 years ago

  • Related to Bug #10546: Reduce the number of interfaces duplicates added
Actions #4

Updated by Marek Hulán over 8 years ago

  • Related to Bug #10805: VLAN interface attached to bond is wrongly created as Bond added
Actions #5

Updated by Marek Hulán over 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Marek Hulán

I think I found the cause. The issue is that bond is virtual interface which is attached_to ''. When physical interface identifier changes we modify all virtual interfaces of host that has attached_to set to previous identifier value. Since bond is usually imported (and persisted) before primary interface, when primary interface identifier is set for the first time (after provisioning) its identifier changes from '' to 'ens7f0' and we change bond's attached_to from '' to 'ens7f0' and then we even change the identifier (that is required for vlans and aliases). So we have to skip changes where original identifier was not set. Not sure if this also solves the duplication issue (could be) but I'll look at that in #10607

Actions #6

Updated by The Foreman Bot over 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2485 added
  • Pull request deleted ()
Actions #7

Updated by Marek Hulán over 8 years ago

  • Related to Bug #10607: bonding on ubuntu causes foreman to create an interface after each ubuntu server reboot added
Actions #8

Updated by Dominic Cleal over 8 years ago

  • translation missing: en.field_release set to 62
Actions #9

Updated by Marek Hulán over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF