Project

General

Profile

Actions

Bug #24689

open

Unable to change a host's primary interface

Added by Daniel Kraemer over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

We used to create bond interfaces after provisioning, because the community-templates for preseed doesn't support creation of bonds. Somehow the bond-interfaces find their way into foreman and are listed as unmanaged devices. Unfortunately they also claim the IP, which belonged to the primary/provision interface, now. When we take a look at the interfaces (attachment) we see the mess.

This leads to a situation where foreman doesn't let us edit the Host (for rebuilding with new os, we didn't touch the interfaces), with the errors:
  • "IPv4 DNS record img04.maastricht/172.16.220.56 already exists"
  • "Conflict - IPv4 DNS record img04.maastricht/172.16.220.56 already exists"

So i want to move the fqdn from eth0 to bond0 (where the IP is now) and attach eth0 and eth1 to bond0 and also make bond0 managed/primary/provision, so it matches the "real world". But when i do it, i get "DNS name is already taken" at bond0.

This bug looks familiar to: https://projects.theforeman.org/issues/10602

We are also working on a update of the preseed-template-snippit that provides bond-functionality, it's is heavily based on the kickstart network-setup, but that's just a side information why we want to move fqdn/primary/provision interface now.


Files

Selection_031.png View Selection_031.png 58.3 KB Daniel Kraemer, 08/22/2018 01:43 PM

No data to display

Actions

Also available in: Atom PDF