The power management command is sent by the engine via a proxy host. That means you need at least one more host to act as proxy. The engine itself doesn't need to access the bmc network directly. Just like the engine needs no access to the atorage network to perform storage manipulations.

I think in some recent versions fencing by the engine was introduced, but I don't have a setup in front of me to verify.

On Sep 29, 2017 11:13 PM, "~Stack~" <i.am.stack@gmail.com> wrote:

On 09/29/2017 05:31 PM, Dan Yasny wrote:
> You need more than one host for power management
>

Seriously?? I didn't see anything like that in the docs...Maybe I just
missed it.

Also, why wouldn't it still validate? It should still be able to talk to
the interface over the BMC/IPMI network. The fact that I can run the
equivalent test on the command line makes it seem like it should at
least be able to check via the test. Obviously, it would be silly for it
to try to manage itself, but it could at least verify that the
configuration is valid, right?

I have more hosts that I'm going to add, I was just hoping to do those
via the Foreman integration instead of manually building them. Since I'm
not quite ready for that, I will just build a second host on Monday and
report back.

Thanks for the feedback. I would have never guess that as a possibility. :-)

~Stack~