Bug #10566
closed
Unique interface identifier requirement prevents host from being edited if duplicate identifier exists
Added by Patrick Mulrooney about 9 years ago.
Updated almost 6 years ago.
Description
Related to #9618.
Before the unique interface identifier validation was introduced we managed to get several hosts with multiple interfaces with the same identifier. Now that we have upgrade to 1.8+ when we attempt to resolve this situation by deleting the duplicate identifiers we are unable to due to the new validation.
This seems like something the validator should check for as it creates a loop. You are unable to resolve the uniqueness requirement, because your interfaces are not unique.
To reproduce...
1. Setup foreman such that a host has multiple interfaces with same identifier
1.5. I believe this can be done in versions prior to 1.8+
2. Upgrade to 1.8+
3. Attempt to remove one of the inter faces from the host.
- Related to Bug #9618: User shouldn't be allowed to create an interface with same identifier of any existing one added
- translation missing: en.field_release set to 56
I'm fancing the same issue from fresh installation v1.8.1
I can't modify anything from that host because one interface is duplicated, but it not possible delete any of the duplicate entry.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2427 added
- Pull request deleted (
- Assignee set to Marek Hulán
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #11247: IP address is invalid, can't add or remove `.` from identifier added
- Related to Bug #16935: updating a NIC's "Device identifier" if it doesn't already have one fails if the "Device identifier" includes a . or : added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by