Bug #11034
closed
network/interfaces validation checks the removed interfaces
Added by Jérôme Vizcaino over 9 years ago.
Updated over 6 years ago.
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
Typo, read: add bond0 with the same mac, ip, fqdn as eth0
- Related to Bug #11031: Cannot remove interface with duplicate name added
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
- Related to Bug #11053: Ethernet interfaces not checked for uniqueness and foreman would not allow to delete. added
- Related to Bug #11251: Unable to save host due to 'some of the interfaces are invalid' error added
- Status changed from New to Assigned
- Assignee set to Marek Hulán
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2672 added
- Pull request deleted (
)
- Translation missing: en.field_release set to 63
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #12034: Validation of unique MAC can result in false positive added
- Bugzilla link set to 1268207
- Related to Bug #12486: Duplicate IP addresses after upgrading from 1.7 -> 1.8 -> 1.9 added
If a 1.9.4 is considered, add this to the backport candidates.
Also available in: Atom
PDF