When provisioning for the first time, "Mac address ... already in use"

Support
1

I have a host which I have never provisioned in The Foreman. However, it
was discovered using Foreman Discovery 2.0.

I am attempting to provision this system, and I am in the "General
Settings" page and I'm looking at the section titled "Interface (Up)". This
interface is up, and should be unknown to DHCP. However, Foreman currently
tells me that "Mac address AA:BB:CC:DD:EE:FF already in use" and I cannot
proceed with provisioning this system until I delete that interface. If I
add the interface back, Foreman gives me the same error again.

I do see the MAC address listed in /var/lib/dhcpd/dhcpd.leases .

How can I troubleshoot this further?

Thank you,

-= Stefan

2

Hello,

> I have a host which I have never provisioned in The Foreman. However, it
> was discovered using Foreman Discovery 2.0.

I assume this is Foreman develop?

> How can I troubleshoot this further?

If this is develop, you need to use Discovery 2.0 only with 1.7. There
were changes merged which are not compatible. We are rolling RC2 out now
only with support of Foreman 1.7.

If this was 1.7, pastebin the dhcpd.leases and Foreman logs.

··· -- Later, Lukas #lzap Zapletal
3

This is with Foreman 1.7.2 and the foreman_discovery-2.0.0-0.1.rc1 RPM.

Perhaps I should wait for RC2. I think if I delete the hosts from the
Discovery screen, I can then provision them via Hosts > New Host.

-= Stefan

-= Stefan

··· On Fri, Jan 30, 2015 at 1:04 AM, Lukas Zapletal wrote:

Hello,

I have a host which I have never provisioned in The Foreman. However, it
was discovered using Foreman Discovery 2.0.

I assume this is Foreman develop?

How can I troubleshoot this further?

If this is develop, you need to use Discovery 2.0 only with 1.7. There
were changes merged which are not compatible. We are rolling RC2 out now
only with support of Foreman 1.7.

If this was 1.7, pastebin the dhcpd.leases and Foreman logs.

–
Later,
Lukas #lzap Zapletal

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/5FRVGVu7pb4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

I am afraid we won't have a fix for this one. Can you pastebin me the
leases file (send it to me directly if you want) and let me know which
MAC address is the failing one?

Also, are you able to try this small oneliner patch on your instance if
it helps? You can skip the tests and only apply the one line to check it
out:

Also it is worth investigating which host already have MAC address
defined.

··· On Fri, Jan 30, 2015 at 12:39:57PM -0800, Stefan Lasiewski wrote: > This is with Foreman 1.7.2 and the foreman_discovery-2.0.0-0.1.rc1 RPM. > > Perhaps I should wait for RC2. I think if I delete the hosts from the > Discovery screen, I can then provision them via Hosts > New Host.

–
Later,
Lukas #lzap Zapletal