Project

General

Profile

Bug #9265

Managed BMC interface does not get a DHCP IP

Added by Nux Ro over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hello,

I have added a host with an uplink as well as a BMC interface (IPMI).
While the host did get an IP address in its appropriate subnet and is working fine, the BMC did not, even though it was added as a "managed" NIC.
An entry for it is nowhere to be seen in the dhcpd.conf or dhcpd.leases.

In the foreman.nics MySQL table I can see the BMC NIC with the correct details.

I'm on CentOS 7 with Foreman 1.7.2 installed via foreman-installer.


Related issues

Related to Foreman - Tracker #2409: NetworkingNew

History

#1 Updated by Dominic Cleal over 7 years ago

The support for additional network interfaces has been revamped for 1.8, so it would be valuable if you're able to try our nightly packages out on a test server to see if the issue remains.

#2 Updated by Nux Ro over 7 years ago

Dominic Cleal wrote:

The support for additional network interfaces has been revamped for 1.8, so it would be valuable if you're able to try our nightly packages out on a test server to see if the issue remains.

Tried 1.8 from http://yum.theforeman.org/nightly/el7/ and BMC managed interfaces are still not added to DHCPD.

#3 Updated by Dominic Cleal over 7 years ago

#4 Updated by Marek Hulán over 7 years ago

It seems to work for me if I specify DNS name. I'll continue investigating but could you please confirm whether you specify it or not? Also it would help if you enabled debug log level for foreman and foreman proxy and uploaded both during new host creation.

#5 Updated by Marek Hulán over 7 years ago

  • Priority changed from High to Normal

We currently require hostname for DHCP orchestration. I reset priority since there's an easy workaround. The proper fix will be more complex.

#6 Updated by Nux Ro over 7 years ago

Marek Hulán wrote:

We currently require hostname for DHCP orchestration. I reset priority since there's an easy workaround. The proper fix will be more complex.

Thanks Marek, I can confirm specifying a "dns name" fixes it, I can work with this.

Also available in: Atom PDF