Bug 1353788 - After cloning of roles you cant select the role nor can you delete them.
Summary: After cloning of roles you cant select the role nor can you delete them.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.2.0
Hardware: All
OS: All
high
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Stanislav Tkachenko
URL:
Whiteboard:
: 1350354 1388718 1457658 (view as bug list)
Depends On:
Blocks: 1416568 1426383
TreeView+ depends on / blocked
 
Reported: 2016-07-08 02:16 UTC by Kim Borup
Modified: 2021-09-09 11:53 UTC (History)
21 users (show)

Fixed In Version: foreman-1.11.0.75-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1416568 1426383 (view as bug list)
Environment:
Last Closed: 2017-05-01 13:52:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screen of acctual problem. (11.56 KB, image/png)
2016-07-08 02:16 UTC, Kim Borup 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15108 0 None None None 2016-08-04 14:10:11 UTC
Foreman Issue Tracker 16828 0 None None None 2017-03-17 13:21:28 UTC
Foreman Issue Tracker 18321 0 None None None 2017-03-17 13:21:48 UTC
Red Hat Product Errata RHBA-2017:1191 0 normal SHIPPED_LIVE Satellite 6.2.9 Async Bug Release 2017-05-01 17:49:42 UTC

Description Kim Borup 2016-07-08 02:16:41 UTC 
Created attachment 1177510 [details]
Screen of acctual problem.

Description of problem:
When you in satellite 6.2 clone a role, in this case a very restrictive role for a group of users, clone of that role becomes greyes out like the Anonymous or Default user role, you can add a filter to it, but you can not delete it nor can you assign it to a user. 

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

How reproducible:

All the time

Steps to Reproduce:
1. Select Administer -> roles
2. Clone any role build in or manualy created.
3. 

Actual results:
greyed out role you cant delete, nor assign to a user. 

Expected results:

A clone of a role that you can select and attach to a user. 

Additional info:

This is a work in progress at a customer site for a poc before the final 6.2 release.
Comment 2 Brad Buckingham 2016-07-08 19:35:28 UTC 
Ohad, is this the expected behavior when cloning Roles?
Comment 3 Marek Hulan 2016-08-04 14:10:11 UTC 
It's not expected behavior.
Comment 4 Bryan Kearney 2016-08-04 16:16:17 UTC 
Upstream bug assigned to mhulan
Comment 5 Bryan Kearney 2016-08-04 16:16:22 UTC 
Upstream bug assigned to mhulan
Comment 6 Marek Hulan 2016-08-11 08:31:22 UTC 
*** Bug 1350354 has been marked as a duplicate of this bug. ***
Comment 7 Bryan Kearney 2016-08-11 12:16:52 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/15108 has been closed
Comment 9 Roman Plevka 2016-10-20 10:37:54 UTC 
VERIFIED
on sat6.3 snap#5

cloned built-in roles are now able to be deleted.
Comment 10 Marek Hulan 2016-10-26 07:32:51 UTC 
*** Bug 1388718 has been marked as a duplicate of this bug. ***
Comment 12 Satellite Program 2017-02-23 21:08:39 UTC 
Please add verifications steps for this bug to help QE verify
Comment 16 Lukas Zapletal 2017-02-24 15:26:58 UTC 
REL ENG: TWO patches required, both small:

https://github.com/theforeman/foreman/pull/3925
https://github.com/theforeman/foreman/pull/4244

I already filed MR for the former one.
Comment 18 Lukas Zapletal 2017-03-21 13:44:08 UTC 
Sure it's trivial whitespace.
Comment 20 Lukas Zapletal 2017-03-21 13:52:19 UTC 
QA Steps to Reproduce:
1. Select Administer -> roles
2. Clone any role build in or manualy created.
3. Attempt to delete it, it should be possible
Comment 21 Stanislav Tkachenko 2017-03-30 08:41:17 UTC 
Verified on Sat 6.2.9-1, both built-in (Default User) and manually created roles can be cloned, cloned roles can be edited and deleted.
Comment 23 errata-xmlrpc 2017-05-01 13:52:53 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.

https://access.redhat.com/errata/RHBA-2017:1191
Comment 24 Marek Hulan 2017-06-12 13:46:01 UTC 
*** Bug 1457658 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.