Hide Forgot
Created attachment 1209195 [details] wrong filtering on applicable content hosts list Description of problem: `Filter by Environment` drop-down on Content-Hosts tab of Errata page seems not working and showing content hosts from all environments. Version-Release number of selected component (if applicable): Sat6.3 Beta SNAP 3 How reproducible: Always Steps to Reproduce: 1. Make sure you have errata and at least 2 applicable hosts in different environments 2. Navigate to Content -> Errata -> (errata-id) -> Content Hosts, try to filter hosts by environment Actual results: `Filter by Environment` drop-down doesn't filter content hosts by environment and shows all the content hosts regardless of selected environment. Expected results: `Filter by Environment` drop-down should correctly filter list of hosts by environment Additional info:
Created redmine issue http://projects.theforeman.org/issues/17208 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17208 has been resolved.
This doesn't work for me on 6.3.0 snap 9. When selecting an environment I don't see the environment id included in the request to /api/v2/hosts/post_index and when I click the 'x' the environment is not cleared from the select.
(In reply to Walden Raines from comment #4) > This doesn't work for me on 6.3.0 snap 9. When selecting an environment I > don't see the environment id included in the request to > /api/v2/hosts/post_index and when I click the 'x' the environment is not > cleared from the select. Sorry, I now see that the environment is included in the search query but the selection still doesn't clear when the 'x' is clicked. It is removed from the query but the UI isn't updated.
Hello, We would like to have update on this as we need to inform the customer about the progress. Thanks, Neha
This patch has been verified in 6.3; you can expect it in 6.3 GA.
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