You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wondering if it's possible to have this plugin disable a node when it's renamed in Foreman (its old name). Sort of on the line of the DHCP, DNS functionalities that update the other services after a host is renamed.
Recently had an issue where a number of physical hosts were renamed in Foreman and then rebuilt. PuppetDB still held the old names along with all their exports -- which didn't make our monitoring system (fed from puppet) happy trying to monitor 2 separate hosts with the same IP address.
The text was updated successfully, but these errors were encountered:
I think that's reasonable, we can catch the event in an after_validation filter. I'm not sure I can get to it soon, but a patch would be appreciated and carefully reviewed 😄
Wondering if it's possible to have this plugin disable a node when it's renamed in Foreman (its old name). Sort of on the line of the DHCP, DNS functionalities that update the other services after a host is renamed.
Recently had an issue where a number of physical hosts were renamed in Foreman and then rebuilt. PuppetDB still held the old names along with all their exports -- which didn't make our monitoring system (fed from puppet) happy trying to monitor 2 separate hosts with the same IP address.
The text was updated successfully, but these errors were encountered: