Created attachment 1313988 [details] screenshot of the created filter rule Description of problem: when creating a filter rule, the architecture information is not passed to katello setting sev: high as that might have interesting results on the clients Version-Release number of selected component (if applicable): tfm-rubygem-hammer_cli_foreman-0.10.2-1.el7sat.noarch tfm-rubygem-hammer_cli-0.10.2-1.el7sat.noarch tfm-rubygem-hammer_cli_katello-0.10.0-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. create a filter with name=foo, arch=x86_64, version=1234 hammer content-view filter rule create --content-view-filter-id 3 --name foo --arch x86_64 --version 1234 Actual results: The created rule has no architecture set (according to the WebUI) Expected results: The created rule has an architecture set Additional info:
bonus, it also creates rules with invalid arch values passed: # hammer content-view filter rule create --content-view-filter-id 3 --name fooaaa --arch burp --version 1234 Filter rule created
Created redmine issue http://projects.theforeman.org/issues/20749 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20749 has been resolved.
Verified on Sat 6.3 snap 24, architecture is correctly assigned to the cv filter rule
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/RHSA-2018:0336