Bug 1353788
| Summary: | After cloning of roles you cant select the role nor can you delete them. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Kim Borup <kborup> | ||||
| Component: | Users & Roles | Assignee: | Marek Hulan <mhulan> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Stanislav Tkachenko <stkachen> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.2.0 | CC: | amasolov, bbuckingham, bkearney, brcoca, cwelton, dcaplan, dhawke, egolov, ehelms, hprakash, jcallaha, kelly.brown1, lzap, mhulan, ohadlevy, rplevka, sauchter, sshtein, stkachen, vgunasek, zhunting | ||||
| Target Milestone: | Unspecified | Keywords: | PrioBumpPM, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | foreman-1.11.0.75-1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1416568 1426383 (view as bug list) | Environment: | |||||
| Last Closed: | 2017-05-01 13:52:53 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1416568, 1426383 | ||||||
| Attachments: |
|
||||||
Ohad, is this the expected behavior when cloning Roles? It's not expected behavior. Upstream bug assigned to mhulan Upstream bug assigned to mhulan *** Bug 1350354 has been marked as a duplicate of this bug. *** Moving to POST since upstream bug http://projects.theforeman.org/issues/15108 has been closed VERIFIED on sat6.3 snap#5 cloned built-in roles are now able to be deleted. *** Bug 1388718 has been marked as a duplicate of this bug. *** Please add verifications steps for this bug to help QE verify 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. Sure it's trivial whitespace. 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 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. 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 *** Bug 1457658 has been marked as a duplicate of this bug. *** |
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.