Bug #6492


IPMI boot and power unaccessible to non-admin users

Added by Daniel Lobato Garcia about 10 years ago. Updated about 6 years ago.

Target version:
Fixed in Releases:
Found in Releases:


When any user tries to run IPMI boot or power, no matter what role is applied to them it fails.

The call always return a 404 not found, right after a filter chain halted as
:find_by_name rendered or redirectered.

The only workaround is to make every user who makes IPMI calls an admin. I see this as a hint that it has something to do with roles.

Related issues 1 (0 open1 closed)

Related to Foreman - Bug #5994: Power and Console links are disabled for non-admin usersClosed05/30/2014Actions
Actions #1

Updated by Dominic Cleal about 10 years ago

  • Related to Bug #5994: Power and Console links are disabled for non-admin users added
Actions #2

Updated by Kevin Mullin about 10 years ago

I believe I was the person who originally reported this issue on IRC.

Daniel helped me debug as much as we could, it definitely appears to revolve around Roles being set for a user.

This is actually a huge blocker for our usage of foreman, where we want to give developers access to a subset of our machines. We want to give them total control of the hardware, including the ability to set 'ipmi_boot?ipmi_device=pxe' the host.

Ironically, the user who has Roles set for it, can easily 'reboot' the box so the BMC portion of the roles works for that, just not for setting the 'ipmi_boot' device.

Please let me know if I can provide any more information for this bug, as its easily reproducible in our environment.

Actions #3

Updated by Gael Queri about 8 years ago

Same issue with Foreman 1.9.0

Actions #4

Updated by Joe Mader almost 8 years ago

This is a blocking problem for our shop as well - same use case as Kevin Mullin. We are using Foreman v1.10.

Actions #5

Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request added
Actions #6

Updated by Daniel Lobato Garcia almost 8 years ago

I've submitted a fix via - I believe it's only the ipmi_boot action that suffers from this problem. The power_hosts permission works fine when applied to users in my environment. Let me know if that's not your case (and which version of Foreman you use)

Actions #7

Updated by Daniel Lobato Garcia almost 8 years ago

  • Target version set to 1.5.2
Actions #8

Updated by Anonymous almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #9

Updated by Dominic Cleal almost 8 years ago

  • Translation missing: en.field_release set to 189

Also available in: Atom PDF