Project

General

Profile

Actions

Bug #10602

closed

Unable to change a host's primary interface

Added by Trey Dockendorf over 9 years ago. Updated over 7 years ago.

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

Description

If I have a host with a setup like this:

eth0
eth1: primary + provisioning named test.domain

And I attempt to change eth0 to the primary interface because eth1 is actually on a private network I get a validation error of "Some of the interfaces are invalid. Please check the table below." and eth0 is highlighted. I select Edit for eth0 and it says the DNS name is already taken. If I attempt this operation again but also remove the DNS name and domain from eth1 the validation still fails for the same reason. The only way I've been able to modify a host's primary interface has been by giving the new primary interface a completely new name. This results in the host having a new, incorrect, FQDN which I then have to go back in and change back to the original hostname.

My guess is the validation is failing because the removal of the DNS name from eth1 hasn't taken place yet so the uniqueness constraint is validated.

Actions

Also available in: Atom PDF