Project

General

Profile

Bug #11031

Cannot remove interface with duplicate name

Added by Jérôme Vizcaino about 6 years ago. Updated about 3 years ago.

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

Description

Somehow, after migrating from foreman 1.7.4 to 1.8.2, duplicate interfaces appeared (especially on hosts with virtual nics and bridges).

Trying to remove duplicate interfaces simply does not work.

Howto reproduce:
  • locate a host with duplicated interfaces (two br0 for example)
  • try to remove one of the 'br0'
  • submit
  • application complains that one of the 'br0' are invalid

Related issues

Related to Foreman - Bug #11034: network/interfaces validation checks the removed interfaces Closed2015-07-07
Related to Foreman - Bug #11053: Ethernet interfaces not checked for uniqueness and foreman would not allow to delete.Duplicate2015-07-08
Has duplicate Foreman - Bug #11410: Unable to delete invalid interfaces from foremanDuplicate2015-08-18
Has duplicate Foreman - Bug #11743: Multiple 'wwan0' interfaces prevent rebuilding of machineDuplicate2015-09-09

Associated revisions

Revision 1e7822a5 (diff)
Added by Marek Hulán almost 6 years ago

Fixes #11031 - ignore identifiers of interfaces being destroyed

Revision bd3f3260 (diff)
Added by Marek Hulán almost 6 years ago

Fixes #11031 - ignore identifiers of interfaces being destroyed

(cherry picked from commit 1e7822a586b6e4f288823df0b9419ef2749d6b8c)

Revision cfa245cf (diff)
Added by Marek Hulán almost 6 years ago

Fixes #11031 - ignore identifiers of interfaces being destroyed

(cherry picked from commit 1e7822a586b6e4f288823df0b9419ef2749d6b8c)

History

#1 Updated by Dominic Cleal about 6 years ago

  • Category set to Network

Can you share the log from when you submit the form, and/or what the errors are (if shown) on the individual interfaces?

#2 Updated by Dominic Cleal about 6 years ago

  • Related to Bug #11034: network/interfaces validation checks the removed interfaces added

#3 Updated by Marek Hulán about 6 years ago

  • Related to Bug #11053: Ethernet interfaces not checked for uniqueness and foreman would not allow to delete. added

#4 Updated by Dominic Cleal almost 6 years ago

  • Has duplicate Bug #11410: Unable to delete invalid interfaces from foreman added

#5 Updated by Jason Frisvold almost 6 years ago

FWIW, I wasn't able to see any errors in the logs when I was having this problem. I'll admit, though, I'm not sure which logs I should be checking. In my instance, I was looking at the foreman production.log in /var/log/foreman as well as the logs in /var/log/foreman-proxy.

#6 Updated by Marek Hulán almost 6 years ago

  • Assignee set to Marek Hulán

#7 Updated by Marek Hulán almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2627 added
  • Pull request deleted ()

#8 Updated by Marek Hulán almost 6 years ago

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

#9 Updated by Dominic Cleal almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 84

#10 Updated by Dominic Cleal almost 6 years ago

  • Has duplicate Bug #11743: Multiple 'wwan0' interfaces prevent rebuilding of machine added

Also available in: Atom PDF