Setting host to unmanaged keeps DHCP record

Support
,
1

Hello,

I’ve got the following situation:
I add a host to Foreman, then I build it. Everything goes fine, the OS gets installed and I’m able to log into to the host via SSH. I then set the host as unmanaged. However, upon inspecting the dhcpd.leases file on the responsible smart-proxy, the host still has a valid lease.

My question is: Is this expected behavior? Should Foreman keep a DHCP record for a host that it doesn’t build?

I’m running Foreman 3.1.0

All the best,
Kaloyan

2

Sounds like a bug, managed-unmanaged workflow is not greatly tested.

3

Where can I open a bug report describing exactly how to reproduce it?

4

But I don’t expect this to be fixed anytime soon, this workflow is not widely used.