Bug 1305058

Summary: [Sat6] hammer content-view filter rule create does not validate input
Product: Red Hat Satellite Reporter: Stuart Auchterlonie <sauchter>
Component: Hammer - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.6CC: mshira, sthirugn, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 17:58:34 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:
Bug Depends On:    
Bug Blocks: 1316897    

Description Stuart Auchterlonie 2016-02-05 13:47:19 UTC 
Description of problem:

There is no validation of rpm packages added to filter rules via hammer

This can be demonstrated using an rpm include filter for a content view

The package name being passed in is not validated. So you can add "rpms"
called "this_does_not_exist"


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

6.1.6

How reproducible:

100%


Steps to Reproduce:
1. Create an rpm include content view filter.
2. Add a non existing package

# hammer --username=admin --password=<password> content-view filter rule create --organization=org-example --content-view='filter test' --content-view-filter='test_filter' --name does_not_exist

Will add packge name "does_not_exist" to the included rpms


Actual results:

See above

Expected results:

There should be some validation that the requested package exists


Additional info:
Comment 5 Bryan Kearney 2016-08-04 20:19:16 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 6 Bryan Kearney 2018-09-04 17:58:34 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.