Foreman » Smart Proxy

I think it has to do with the privilege level (-L <privlvl>]). My co-worker has added the ipmi users as "OPERATOR" instead of the all mighty "ADMINISTRATOR" privilege. This is good as it is not very secure to use the admin user for these things. I tested with an admin account and it works fine.

-L <privlvl>
Force session privilege level. Can be CALLBACK, USER, OPERATOR, ADMINISTRATOR. Default is ADMINISTRATOR.

So I tried modifiying "/usr/lib/ruby/gems/1.8/gems/rubyipmi-0.7.0/lib/rubyipmi/ipmitool/connection.rb"

        # default to IPMI 2.0 communication, this means that older devices will not work
        # Those old servers should be recycled by now, as the 1.0, 1.5 spec came out in 2005ish and is 2013.
        @options["L"] = "Operator" 
        @options["I"] = "lanplus" 

But that doesn't help. Anything else I have to modify to make this work?

is this a duplicate of #2749 which is now closed?

Rubyipmi 0.8.1 supports passing in the privilege type, but you would need to expose this to the UI or make it a setting in the smart-proxy bmc settings file. Additionally, if we know the exact error message from the impi provider we can actually have rubyipmi react to the error message and try a different privilege type. It might be worth while to add a test connection function to rubyipmi and even additionally pass back a supported list of commands given the privilege type. I suspect the privilege type will change from host to host depending on manufacture of system.

With this fix this now allows the user to pass an options hash in the request JSON body like

"{" 
"options": {"privilege": "OPERATOR"},
"bmc_provider": "freeipmi",
"}" 

While this ticket allowed parameters to pass through to foreman, there is another issue related to parameters not being gathered from the body of the request.

Bug #10116