Project

General

Custom queries

Profile

Actions
Copy link

Bug #10566

closed

Unique interface identifier requirement prevents host from being edited if duplicate identifier exists

Added by Patrick Mulrooney almost 10 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
Marek Hulán
Category:
Network
Target version:
1.8.2
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/2427
Fixed in Releases:
Found in Releases:
1.8.1
Red Hat JIRA:

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.

Related issues 3 (0 open — 3 closed)

Related to Foreman - Bug #9618: User shouldn't be allowed to create an interface with same identifier of any existing oneClosedMarek Hulán03/03/2015Actions
Related to Foreman - Bug #11247: IP address is invalid, can't add or remove `.` from identifierResolved07/29/2015Actions
Related to Foreman - Bug #16935: updating a NIC's "Device identifier" if it doesn't already have one fails if the "Device identifier" includes a . or :ClosedSean O'Keeffe10/14/2016Actions

Added by Marek Hulán almost 10 years ago

Revision a6b8542a (diff)

Fixes #10566 - allow identifier modifications that do not change interface type

Added by Marek Hulán almost 10 years ago

Revision f967d733 (diff)

Fixes #10566 - allow identifier modifications that do not change interface type

(cherry picked from commit a6b8542a0e1a7eb0d71fdd1d328b224669e3010b)

Actions
Copy link

Also available in: Atom PDF