BMC plugin depends on location?

Support
1

Problem:
BMC plugin timeouts as discovery goes over random foreman-proxy
Configuration of BMC plugin is on all proxies same, true and ipmitool, which is installed everywhere.
We have more foreman-proxies in one default-location and every proxy has own host-group for provisioning.
Expected outcome:
Would be used same foreman-proxy, which provisioned host, to connect to BMC

Foreman and Proxy versions: 1.21.3 and 1.22.1

Foreman and Proxy plugin versions: 1.22.1

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)

logs
2

Hello and please elaborate this statement. What do you mean by “to go over”.

Discovered nodes are matched via subnets and organization/location from these subnets. If you have multiple org/loc associated within those subnets, they are picked RANDOMLY. It’s terrible but it’s documented behavior.

3

Hi Izap,

I realized that there was misunderstanding of our infrastructure when I added BMC to all proxies.
I disabled them on all proxies but on one Proxy connected to IPMI network and now they work well.

Thanks for your answer and explanation :slight_smile: