Foreman-proxy bmc doesn't work after upgrade from 3.14 to 3.15/3.16

dseira · September 26, 2025, 12:06pm

Problem:

Having a foreman 3.14 working properly with BMC support with ipmitool; after upgrade to foreman 3.15 (and 3.16 same too) it stops working; always shows BMC as powered off.

Disabling/re-enabling the bmc in the foreman-proxy /etc/foreman-proxy/settings.d/bmc.yml doesn’t work.

That file has the following content:

# Can be true, false, or http/https to enable just one of the protocols
:enabled: true

# Available providers:
# - freeipmi / ipmitool - requires the appropriate package installed, and the rubyipmi gem
# - redfish - requires the redfish_client gem
# - shell - for local reboot control (requires sudo access to /sbin/shutdown for the proxy user)
# - ssh - limited remote control (status, reboot, turn off)
:bmc_default_provider: ipmitool

Enabling the loglevel debug doesn’t show any specific error about what is happening.

I’ve also enabled a tcpdump to see if it is sending some request to the BMC but there is any request.

It is already installed ipmitool and rubygem-rubyipmi:

ipmitool-1.8.18-27.el9.x86_64
rubygem-rubyipmi-0.12.0-1.el9.noarch

Executing the ipmitool in the command line it works as expected:

sudo -u foreman-proxy ipmitool -I lanplus -H 1.2.3.4 -U user1 chassis power status

Chassis Power is on

I don’t really know what is happening and what else do to fix that.

Expected outcome:

As I’ve said before, BMC support was working perfectly in foreman 3.14; neither 3.15 nor 3.16 are working.

Foreman and Proxy versions:

foreman-proxy-3.15.0-1.el9.noarch
foreman-3.15.0-1.el9.noarch
foreman-proxy-3.16.0-1.el9.noarch
foreman-3.16.0-1.el9.noarch

Foreman and Proxy plugin versions:

Distribution and version:

OS is Rocky Linux 9.6 (upgraded from RL8 using leapp as suggested by your guide).

Other relevant data:

dseira · September 29, 2025, 10:51am

Found the problem. The update of the rubygem-rubyipmi from 0.11.1 to 0.12.0 broke the ipmi support.

As a workaround:

github.com/logicminds/rubyipmi

v0.12.0 remote access is broken with both FreeIPMI and ipmitool

opened 05:24PM - 24 Jul 25 UTC

tyuxar

Hi, I've had a Ruby script I wrote to learn the language and automate remote ba…ckups. It uses rubyipmi to turn on a remote server. It's been working well for months with v0.11.1, but today, after upgrading to v0.12.0 (FreeBSD `pkg upgrade`) it stopped working. I've been using ipmitool, but switching to freeipmi gives the same result. I also tried both versions of the gem on a Devuan Daedalus VM, too, and ended up the same way. I used `gem install --user-install ...` this time, so this rules out possible interference from the FreeBSD packager. Unfortunately I am not a well-versed Ruby developer (I'm learning the language), and could not fully debug it (yet). What infos can I share with you to help debugging?

dseira · December 4, 2025, 1:09pm

The problem is still there and since the developer of the rubygem-rubyipmi doesn’t show any interest on fixing this (issue opened on Jul and I push up on Sept with additional info), could you please change the dependancy on the foreman 3.16/3.17 (and next comming) to return to 0.11.1?

Thanks.

sbible · December 17, 2025, 12:24am

I’ll see if we can get an issue created to look into this.

sbible · December 17, 2025, 6:04pm

Alright, create Foreman-proxy bmc doesn’t work after upgrade from 3.14 to 3.15 and onward to track this, and an associated downstream issue in the Satellite JIRA project.

iballou · December 17, 2025, 6:44pm

38966 is the redmine