Hide Forgot
Description of problem: Filtering content hosts so 0 records is returned makes the page to say "You currently don't have any Content Hosts, you can register one by clicking the button on the right and following the instructions.", which is untrue, becouse I have lots of content hosts, I have just used incorrect filter. Version-Release number of selected component (if applicable): satellite-6.2.0-8.2.beta.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Have bunch of content hosts registered 2. Go to Hosts -> Content Hosts and enter "name = non_existet" as a search term Actual results: No results are shown (GOOD) This message is shown (BAD): You currently don't have any Content Hosts, you can register one by clicking the button on the right and following the instructions. Expected results: Page functionality should be adjusted that this message is shown only when you have no content hosts at all.
I do not see us adressing this in the next few releases. I am therefore closing this out. If you feel that this is a mistake, please feel free to re-open with additional information.
Have re-opened this bug, as it can also occur when you use a valid filter in content hosts. Doing All Hosts and search for location = AMERICAS it returns the hosts on that specific location (3 of them in my case) Doing content hosts and search for location = AMERICAS, I get a message stating: You currently don't have any Content Hosts, you can register one by clicking the button on the right and following the instructions. When there should be 3 of them in the AMERICAS location.
Hello, this BZ was only about wording/in-correctness of the message, not about actual filters used. I propose you create new BZ for your issue to avoid confusion. Thank you!
Thanks Jan. Will go ahead and create a new bug.
Have raised bug 1439801 for the case where location search fails.
Looking at 6.3 code, there is no longer an erorr message shown, Instead, the user is shown an empty page. I am therefore closing this as nextrelease as it will be resolved in 6.3.