Bug 1699607

Summary:	Host Collection filtering can't view facts
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Users & Roles	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Radovan Drazny <rdrazny>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4	CC:	bkearney, dhlavacd, mhulan, rjerrido
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused	Flags:	tasander: needinfo-
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-07 13:43:01 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 Taft Sanders 2019-04-14 06:04:52 UTC

Description of problem:
When creating a role to view only hosts of a specific host collection and using the search parameters set to host_collection = <HOST COLLECTION>. Facts are not viewable for these hosts

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

How reproducible:
Every time

Steps to Reproduce:
1. Clone the Viewers role
2. Set the search parameter for the filter "Host" to "host_collection = <HOST COLLECTION>
3. View a host's facts from the either the Hosts page or the Facts page

Actual results:
Oops, we're sorry but something went wrong Can't join 'Host::Base' to association named 'host_collections'; perhaps you misspelled it?


Expected results:
Facts to be shown for all hosts of the host collection

Additional info:
This is breaking functionality to dynamically sync inventory from Satellite by host collection

Comment 3 Marek Hulan 2019-11-21 12:06:38 UTC

This seems as BZ 1569395, which has been fixed in 6.5, could you please check the upgrade resolves your issue?

Comment 4 Bryan Kearney 2020-02-07 13:43:01 UTC

No feedback recieved, closing this as a dupe.

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