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: