What is the recommended/proper procedure for when you need to replace the
NIC in a host being managed by Foreman? When the host comes back up it
will have a new MAC address. Will Foreman figure out that the host's MAC
has changed from Puppet or is it necessary to manually change the MAC
address?
The issue being that we don't want it to show up under "Discovered hosts"
and have people thinking they can provision it.
> What is the recommended/proper procedure for when you need to replace the
> NIC in a host being managed by Foreman? When the host comes back up it will
> have a new MAC address. Will Foreman figure out that the host's MAC has
> changed from Puppet or is it necessary to manually change the MAC address?
Yes, in general, however, see the next comment…
> The issue being that we don't want it to show up under "Discovered hosts"
> and have people thinking they can provision it.
Ah, with discovery, of course, your new MAC won't be present on the
TFTP server. I'd suggest temporarily stopping Puppet on the host (so
the mac stops being updated), changing the mac in Foreman (so the DHCP
and TFTP records are updated) and then replace the NIC.
Of course, this only works if you know the MAC in advance. If you
don't, then the other option is to cancel the boot into discovery at
the pxe prompt by hand (or temporarily set the default boot to
localboot). In this sceanrio, Foreman should notice the change of
mac, but I'm not 100% convinced it would update the tftp record.
Do let us know how you get on with this - it's something we need to
document better, especially for discovery.
Greg
···
On 6 February 2015 at 15:43, Dan McDougall wrote: