Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1330825

Summary: filtering content hosts so 0 records is returned makes the page to say "You currently don't have any Content Hosts..."
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: Content ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NEXTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: afox, bbuckingham, bkearney, eddie.quinteros, james.hofmeister
Target Milestone: UnspecifiedKeywords: Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1439801 (view as bug list) Environment:
Last Closed: 2017-08-11 14:20:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Hutař 2016-04-27 04:57:51 UTC
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.

Comment 2 Bryan Kearney 2017-03-27 20:29:27 UTC
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.

Comment 3 afox@redhat.com 2017-03-29 15:42:40 UTC
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.

Comment 4 Jan Hutař 2017-04-04 06:59:04 UTC
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!

Comment 5 afox@redhat.com 2017-04-06 14:31:21 UTC
Thanks Jan. Will go ahead and create a new bug.

Comment 6 afox@redhat.com 2017-04-06 14:38:30 UTC
Have raised bug 1439801 for the case where location search fails.

Comment 7 Bryan Kearney 2017-08-11 14:20:03 UTC
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.

Comment 8 Bryan Kearney 2017-08-11 14:20:20 UTC
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.