Created attachment 1314228 [details] Screenshot with hidden message for Content Hosts Description of problem: When searching for katello entities, e.g Activation Keys, and no results found, UI shows empty table and message "Your search returned zero Activation Keys." However, for content hosts entire table, including message, is hidden. Version-Release number of selected component (if applicable): Satellite 6.3 Snap 11: * satellite-6.3.0-16.0.beta.el7sat.noarch * katello-3.4.4-2.el7sat.noarch * foreman-1.15.3-1.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. navigate to Content Hosts 2. Search using some invalid search criteria, e.g. `name=noname` 3. Check whether message 'Your search returned zero Content Hosts.` is displayed. Actual results: Message is hidden. Expected results: Message should be displayed. Additional info:
Created redmine issue http://projects.theforeman.org/issues/20696 from this bug
I'm not able to reproduce this bug upstream or in the sat63-qa-rhel7 box. I believe it's probably been fixed in the katello 3.4.5 release. I'll attached a screenshot to show the table and message being displayed for Content Hosts when no hosts match the search.
Created attachment 1326127 [details] Content Hosts search showing message
Hi Stanislav, can you do a quick retest of this issue on the latest 6.3 snap and let us know if you still see it? If the issue persists, we may need to get some additional details to see if there is anything different in our environments or procedures. Thanks!
(In reply to Brad Buckingham from comment #5) Hi Brad, I can see proper message on latest 6.3 build, so looks like it is fixed.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20696 has been resolved.
Thanks Stanislav! Based upon the feedback, I am going to move this to VERIFIED. Please feel free to update it, if something changes.
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