Bug #5994

Power and Console links are disabled for non-admin users

Added by Dylan Charleston over 3 years ago. Updated about 3 years ago.

Status:Closed
Priority:High
Assigned To:Dmitri Dolguikh
Category:Authorization
Target version:Sprint 25
Difficulty: Bugzilla link:1110361
Found in release:1.5.0 Pull request:
Story points-
Velocity based estimate-
Release1.5.2Release relationshipAuto

Description

I just upgraded from 1.4.0 to 1.5 and noticed that all non-admin users aren't able to power or connect to the console on VMWare hosts' page. I've verified the roles to make sure "power_compute_resources_vms" and "console_compute_resources_vms" are allowed for these hosts, but the buttons continue to be disabled. The users can access https://foremanserver/hosts/hostname.domain/console URL directly so it looks like they have permission. This is causing a lot of confusion for our users and it looks like it might just be a bug in the frontend.


Related issues

Related to Foreman - Bug #6492: IPMI boot and power unaccessible to non-admin users Closed 07/04/2014
Duplicated by Foreman - Bug #6746: ovirt VM's power and console buttons are disabled for non... Duplicate 07/23/2014
Blocks Foreman - Tracker #4552: New permissions/authorization system issues New 03/05/2014

Associated revisions

Revision 5aac54d7
Added by Dmitri Dolguikh over 3 years ago

fixes #5994: Power and Console buttons are available to non-admin users with appropriate permissions

History

#1 Updated by Dominic Cleal over 3 years ago

  • Category set to Authentication
  • Status changed from New to Feedback

There are a couple of permissions controlling consoles: check that your users also have "console_hosts" under a Host/Managed filter. The console_compute_resource_vms is used when browsing compute resources I think, while the former is used when browsing hosts. Ditto for "power_hosts".

#2 Updated by Dylan Charleston over 3 years ago

Dominic Cleal wrote:

There are a couple of permissions controlling consoles: check that your users also have "console_hosts" under a Host/Managed filter. The console_compute_resource_vms is used when browsing compute resources I think, while the former is used when browsing hosts. Ditto for "power_hosts".

Thanks Dominic, I already have "view_hosts, create_hosts, edit_hosts, destroy_hosts, build_hosts, power_hosts, console_hosts" configured in the hosts/managed filter with the Unlimited checkbox checked.

#3 Updated by Dominic Cleal over 3 years ago

  • Blocks Tracker #4552: New permissions/authorization system issues added

#4 Updated by Dominic Cleal over 3 years ago

  • Category changed from Authentication to Authorization
  • Status changed from Feedback to New

#5 Updated by Dominic Cleal over 3 years ago

  • Release set to 1.5.2

#6 Updated by Dmitri Dolguikh over 3 years ago

  • Status changed from New to Assigned
  • Assigned To set to Dmitri Dolguikh

#7 Updated by Bryan Kearney over 3 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1110361

#8 Updated by Dominic Cleal over 3 years ago

  • Target version set to Sprint 25

#9 Updated by Dmitri Dolguikh over 3 years ago

  • Status changed from Assigned to Ready For Testing

#10 Updated by Anonymous over 3 years ago

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

#11 Updated by Dominic Cleal about 3 years ago

  • Related to Bug #6492: IPMI boot and power unaccessible to non-admin users added

#12 Updated by Dominic Cleal about 3 years ago

  • Duplicated by Bug #6746: ovirt VM's power and console buttons are disabled for non-admin users even when the required permissions are granted added

#13 Updated by Paul Calabro about 3 years ago

I'm still experiencing this issue with foreman-1.6.0-0.1.RC1.el6.noarch. I'm also using the XenServer plugin.

My user is currently assigned the following roles:

Their permissions are currently set to the following (pretty much just no destroys):

Please let me know if you need any more info.

#14 Updated by Paul Calabro about 3 years ago

You can disregard my previous comment. My issue was related to the unlimited checkbox not being checked. For some reason, even after checking this box "Unlimited" would show nothing. Deleting and re-adding the filters resolved my issue.

Also available in: Atom PDF