Project

General

Profile

Actions

Bug #11034

closed

network/interfaces validation checks the removed interfaces

Added by Jérôme Vizcaino almost 10 years ago. Updated almost 7 years ago.

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

Description

Updating the network interfaces triggers a validation to check for misconfiguration and errors.

Howto reproduce:
  • add an interface with the same mac, ip, fqdn as another interface (say eth1), name it eth2
  • remove eth1
  • submit

Validation fails, explaining that eth1 and eth2 are conflicting (but eth1 should have been removed!)

Another example: try to migrate your primary, provisioning eth0 interface as a bond0
  • add bond0 with the same mac, ip, fqdn as bond0
  • activate provision and primary for bond0
  • eth0 can now be deleted. remove eth0
  • submit

I think this is related to #11031


Related issues 5 (0 open5 closed)

Related to Foreman - Bug #11031: Cannot remove interface with duplicate nameClosedMarek Hulán07/07/2015Actions
Related to Foreman - Bug #11053: Ethernet interfaces not checked for uniqueness and foreman would not allow to delete.Duplicate07/08/2015Actions
Related to Foreman - Bug #11251: Unable to save host due to 'some of the interfaces are invalid' errorResolvedMarek Hulán07/29/2015Actions
Related to Foreman - Bug #12034: Validation of unique MAC can result in false positiveClosedMarek Hulán10/01/2015Actions
Related to Foreman - Bug #12486: Duplicate IP addresses after upgrading from 1.7 -> 1.8 -> 1.9Resolved11/15/2015Actions
Actions #1

Updated by Jérôme Vizcaino almost 10 years ago

Typo, read: add bond0 with the same mac, ip, fqdn as eth0

Actions #2

Updated by Dominic Cleal almost 10 years ago

  • Related to Bug #11031: Cannot remove interface with duplicate name added
Actions #3

Updated by Dominic Cleal almost 10 years ago

  • Category set to Network
Actions #4

Updated by Markus Frosch almost 10 years ago

Got the same problem, the problem seems to be that interface to be deleted are also validated.

When you change an interface to "valid" data - like renaming eth1 to eth2 and removing the ip address, and then delete it. The deletion works

Actions #5

Updated by Marek Hulán almost 10 years ago

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

Updated by Marek Hulán over 9 years ago

  • Related to Bug #11251: Unable to save host due to 'some of the interfaces are invalid' error added
Actions #7

Updated by Marek Hulán over 9 years ago

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

Updated by The Foreman Bot over 9 years ago

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

Updated by Dominic Cleal over 9 years ago

  • Translation missing: en.field_release set to 63
Actions #10

Updated by Marek Hulán over 9 years ago

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

Updated by Marek Hulán over 9 years ago

  • Related to Bug #12034: Validation of unique MAC can result in false positive added
Actions #12

Updated by Bryan Kearney over 9 years ago

  • Bugzilla link set to 1268207
Actions #13

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #12486: Duplicate IP addresses after upgrading from 1.7 -> 1.8 -> 1.9 added
Actions #14

Updated by Dominic Cleal over 9 years ago

If a 1.9.4 is considered, add this to the backport candidates.

Actions

Also available in: Atom PDF