Bug 1861191

Summary: `Content Hosts` should not be loaded in `Any Organization`
Product: Red Hat Satellite Reporter: Anand Agrawal <aagrawal>
Component: Hosts - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Stephen Wadeley <swadeley>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: mmccune
Target Milestone: UnspecifiedKeywords: PrioBumpQA, Regression
Target Release: Unused   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-03 13:08:35 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 Anand Agrawal 2020-07-28 03:10:51 UTC
Description of problem:

Content Hosts lists should not be loaded in Any Organization. 
It should ask for selecting the Organization.

Production.log shows organization blank as below:

~~~
2020-07-28T08:37:30 [I|app|d11be70d] Processing by Api::V2::HostsController#index as JSON
2020-07-28T08:37:30 [I|app|d11be70d]   Parameters: {"organization_id"=>"", "page"=>"1", "paged"=>"true", "per_page"=>"20", "search"=>"", "sort_by"=>"name", "sort_order"=>"ASC", "apiv"=>"v2"}
2020-07-28T08:37:30 [I|app|d11be70d]   Rendering api/v2/hosts/index.json.rabl within api/v2/layouts/index_layout
2020-07-28T08:37:30 [I|app|d11be70d]   Rendered api/v2/hosts/index.json.rabl within api/v2/layouts/index_layout (Duration: 73.0ms | Allocations: 39714)
2020-07-28T08:37:30 [I|app|d11be70d] Completed 200 OK in 128ms (Views: 70.3ms | ActiveRecord: 21.2ms | Allocations: 63822)

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps:
1. Set 'Any Organisation' from the top of the page.
2. Go to Host -> Content Host

Actual results:  Content Hosts are listed


Expected results: It should asks for selecting the Organization


Additional info:

Comment 3 Brad Buckingham 2020-08-03 13:08:35 UTC

*** This bug has been marked as a duplicate of bug 1861970 ***