Foreman picks wrong mac address

Support
1

Hi,

We have a node with a 10Gbps network card : this is our main network card.
But problem : the card name is p2p1, and even if we correctly set the good mac address in foreman for the primary interface, on the next puppet run, the (unused) em1 mac address wrongly replaces the p2p1 mac address…

So I'm wondering how that could be fixed without going into the bios and disabling all other NICs, keeping in mind we're going to add many more such hosts into puppet, so we'd appreciate not beeing forced to update many bioses because of that…

In facter, the interfaces also seem displayed with a wrong "main" interface :
macaddress => F0:1F:AF:D0:E2:06
macaddress_em1 => F0:1F:AF:D0:E2:06
macaddress_em2 => F0:1F:AF:D0:E2:07
macaddress_em3 => F0:1F:AF:D0:E2:08
macaddress_em4 => F0:1F:AF:D0:E2:09
macaddress_p2p1 => 00:0A:F7:24:44:80
macaddress_p2p2 => 00:0A:F7:24:44:82

facter bug ? misconfiguration (can facter be configured ?) ?
For now, the only card with an IP is p2p1…

We have foreman 1.3.1 here.
Facter version : facter-1.7.3-1.el6.x86_64

Thanks

2

You can tell Foreman not to update IP/MAC from incoming facts, look for the
ignore_puppet_facts_for_provisioning setting under the Provisiong tab.

Greg

··· On 9 January 2014 16:25, SCHAER Frederic wrote:

Hi,

We have a node with a 10Gbps network card : this is our main network card.

But problem : the card name is p2p1, and even if we correctly set the good
mac address in foreman for the primary interface, on the next puppet run,
the (unused) em1 mac address wrongly replaces the p2p1 mac address…