Project

General

Profile

Actions

Bug #23951

closed

Config group is not working with customer user role. (Failing with Stack level too deep)

Added by Marek Hulán almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Search
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1560672

Description of problem:

Created a role and set Resource type = Host and Search = Config Group. Assign this role to the user and login with the user which is using this customized role. Go to Hosts page, it shows error = Stack level too deep.

Version-Release number of selected component (if applicable):

Satellite 6.2.12

How reproducible:
Always

Steps to Reproduce:

1. Create a config group.

2.Add a role with resource type = Content Host, Host, Host Collection, Location and Host with config_group (Refer Image = 6.2.12.Customers_Filter-1.png)

3. and log in with that user and go to Hosts page in the satellite. We will get Stack level too deep error.

Actual results:

Facing issue = Stack level too deep error

Expected results:
User should be able to view the all hosts page in satellite.

Additional info:
We have reproduced same on 6.2.12, 6.2.13 and 6.3.0 and we are getting the same error. While reproducing the issue we added some more resource types just confirm the permission details but we got the same error.

Actions #1

Updated by Marek Hulán almost 6 years ago

  • Subject changed from [Satellite 6.2.14] Config group is not working with customer user role. (Failing with Stack level too deep) to Config group is not working with customer user role. (Failing with Stack level too deep)
  • Category set to Search
  • Assignee set to Marek Hulán

this was present since config groups were introduced

Actions #2

Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5698 added
Actions #3

Updated by Tomer Brisker almost 6 years ago

  • translation missing: en.field_release set to 353
Actions #4

Updated by Marek Hulán almost 6 years ago

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

Also available in: Atom PDF