Bug 1388872

Summary: Hammer: override flag is missing in role filter info
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: Users & RolesAssignee: Marek Hulan <mhulan>
Status: CLOSED DEFERRED QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bkearney, 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-03-20 16:22:22 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    

Description Jitendra Yejare 2016-10-26 10:47:45 UTC 
Description of problem:
In CLI hammer, The override flag is missing in role filter info.

Version-Release number of selected component (if applicable):
Sat6 6.3 snap 5.0

How reproducible:
Always

Steps to Reproduce:
1. Create role.
2. Create filter for some overridable resource in role.
3. Override / Dont Override the filter.
4. Attempt to 'info' above filter.

Actual results:
The override flag is missing from info of a filter.

Expected results:
The override flag should be displayed with flags True/False or yes/no or 1/0.

Additional info:
This issue is observed from API GET request as well.
Comment 2 Marek Hulan 2016-10-26 11:44:53 UTC 
Created redmine issue http://projects.theforeman.org/issues/17109 from this bug
Comment 3 Marek Hulan 2016-10-26 11:49:10 UTC 
Requires both linked upstream issues
Comment 4 Bryan Kearney 2016-10-26 12:20:32 UTC 
Upstream bug assigned to mhulan
Comment 5 Bryan Kearney 2016-10-26 12:20:35 UTC 
Upstream bug assigned to mhulan
Comment 6 Bryan Kearney 2016-10-27 15:32:47 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17109 has been resolved.
Comment 9 Bryan Kearney 2017-03-20 16:22:22 UTC 
This bug has an upstream issue. When this issue is resolved, it will be included in the next Satellite release. We will no longer be tracking this downstream. If you feel this should not have been closed, please feel free to re-open with additional details.