Bug 1444216 - Cloning Manager role does not allow the user to choose the organization(s)
Summary: Cloning Manager role does not allow the user to choose the organization(s)
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Marek Hulan
: 1472252 (view as bug list)
Depends On:
Blocks: 1373844
TreeView+ depends on / blocked
Reported: 2017-04-20 21:06 UTC by David Caplan
Modified: 2019-09-26 15:39 UTC (History)
7 users (show)

Fixed In Version: foreman-1.15.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-02-21 16:59:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
error message on clone template page (63.93 KB, image/png)
2017-04-20 21:06 UTC, David Caplan
no flags Details

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18855 0 None None None 2017-06-19 15:53:01 UTC

Description David Caplan 2017-04-20 21:06:11 UTC
Created attachment 1273071 [details]
error message on clone template page

Description of problem:

Unable to clone the manager role while assigning it to a specific org from the selector.

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

How reproducible:
I select administer -> Roles and attempt to create an Org_admin role for an existing organization. I do this by cloning the "locked" Manager role. In the form I can add the name for the new role "org_admin_OrgName" but when I try to select the desired organization, I get an error message "is invalid". Also the text on the tab "Roles" turns red

The placement and FONT for the error message is also part of this BZ. The error message, if necessary, needs to be better placed with more information using a larger font

Steps to Reproduce:
1. clone the manager role
2. rename in the template, then select the desired organization
3. Select submit

Actual results:

See attached
Expected results:

New role is created and it is scoped to the desired org
Additional info:

Comment 1 Marek Hulan 2017-04-21 06:38:27 UTC
Thanks for the report, could you please let me know what snap are you using so I can reproduce locally? Does anything change if you switch to "any context" in top left corner? If you could attach production.log while log level set to debug and SQL logger enabled it would help greatly. Please see the https://access.redhat.com/solutions/2252291 for instructions how to achieve that.

Comment 4 Marek Hulan 2017-06-02 08:14:26 UTC
We didn't get the logs. I think this might be caused by another issue that was not cloning the built-in flag properly. I'll try to reproduce on new 6.3 build but if it's not reproducible I think we can close this.

Comment 5 Marek Hulan 2017-06-19 15:52:44 UTC
This is caused by invalid organization. That is easy to cause by host being assigned to the organization while some of its resources such as subnet not. The fix is in progress, I'll link the related upstream issue.

Comment 6 Marek Hulan 2017-06-19 15:52:58 UTC
Connecting redmine issue http://projects.theforeman.org/issues/18855 from this bug

Comment 9 Satellite Program 2017-06-29 12:02:41 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18855 has been resolved.

Comment 10 Marek Hulan 2017-07-18 11:13:31 UTC
*** Bug 1472252 has been marked as a duplicate of this bug. ***

Comment 12 Bryan Kearney 2018-02-21 16:59:49 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.