Project

General

Profile

Actions

Bug #5994

closed

Power and Console links are disabled for non-admin users

Added by Dylan Charleston almost 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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 3 (1 open2 closed)

Related to Foreman - Bug #6492: IPMI boot and power unaccessible to non-admin usersClosedDaniel Lobato Garcia07/04/2014Actions
Has duplicate Foreman - Bug #6746: ovirt VM's power and console buttons are disabled for non-admin users even when the required permissions are grantedDuplicate07/23/2014Actions
Blocks Foreman - Tracker #4552: New permissions/authorization system issuesNew

Actions
Actions #1

Updated by Dominic Cleal almost 10 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".

Actions #2

Updated by Dylan Charleston almost 10 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.

Actions #3

Updated by Dominic Cleal almost 10 years ago

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

Updated by Dominic Cleal almost 10 years ago

  • Category changed from Authentication to Users, Roles and Permissions
  • Status changed from Feedback to New
Actions #5

Updated by Dominic Cleal almost 10 years ago

  • translation missing: en.field_release set to 18
Actions #6

Updated by Anonymous almost 10 years ago

  • Status changed from New to Assigned
  • Assignee set to Anonymous
Actions #7

Updated by Bryan Kearney almost 10 years ago

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

Updated by Dominic Cleal almost 10 years ago

  • Target version set to 1.8.1
Actions #9

Updated by Anonymous almost 10 years ago

  • Status changed from Assigned to Ready For Testing
Actions #10

Updated by Anonymous almost 10 years ago

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

Updated by Dominic Cleal over 9 years ago

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

Updated by Dominic Cleal over 9 years ago

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

Updated by Paul Calabro over 9 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.

Actions #14

Updated by Paul Calabro over 9 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.

Actions

Also available in: Atom PDF