Bug 1472252

Summary: Satellite throws exception on creating a new/cloned role with taxonomies
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: Users & RolesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: dhlavacd, mhulan
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-18 11:13:31 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: 1373844    
Attachments:
Description Flags
Screenshot Attached none

Description Jitendra Yejare 2017-07-18 10:08:49 UTC 
Created attachment 1300371 [details]
Screenshot Attached

Description of problem:
Creating a new role (or cloning a role to new) with taxonomies assigned to role throws role 'is Invalid' error on satellte6 UI, it doesnt creates the role also deslects the taxonomies which I selected while creating a role.

foreman production logs -> https://pastebin.com/xYpR357N


Version-Release number of selected component (if applicable):
Satellite 6.3 Snap 5

How reproducible:
Always

Steps to Reproduce:
1. Attempt to create a new role (or clone manager role)
2. Select Locations and organizations to it
3. Submit the role

Actual results:
1. UI throws an 'is invalid' error message
2. Role is not created
3. Taxonomies of role are deselected which are assigned while creating host

Expected results:
Role with taxonomies should be created and and no UI exceptions should be displayed.

Additional info:
If I create/clone role without assigning taxonomies then it works
Comment 2 Marek Hulan 2017-07-18 11:13:31 UTC 
I believe this has been already reported and fixed. The fix has been released in 1.15.2, therefore it's not in any snap atm. Now with the new BZ workflow, I'll update the status of original issue from ON_QA to POST with correct fixed_in_version. Thanks for searching duplicate issue within the component before opening new ones.

*** This bug has been marked as a duplicate of bug 1444216 ***
Comment 3 Marek Hulan 2017-07-18 11:15:46 UTC 
A bit more info, the bug that this one duplicated is ON_QA correctly, last snap already contains the fix and is ready to be verified by QE.