Bug 1327700

Summary:	Capsules should only show information about hosts that are associated with it
Product:	Red Hat Satellite	Reporter:	Og Maciel <omaciel>
Component:	Capsule	Assignee:	Shlomi Zadok <szadok>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, mmccune
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-18 16:01:12 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:

Description Og Maciel 2016-04-15 16:10:47 UTC

Description of problem:

This video (https://omaciel.fedorapeople.org/Capsules.m4v) shows that external capsules that are not associated with any existing Satellite hosts displays puppet/puppet ca information for hosts that are not associated with them. Since there are zero hosts managed via this capsule, my expectation is that I should not see them at all when looking specifically at a capsule.

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

* Satellite 6.2.0 SNAP 8.1

How reproducible:


Steps to Reproduce:
1. You'll need at least one extra external capsules and a host that is managed by either the satellite or the external capsule
2. 
3.

Actual results:

Puppet and Puppet CA information for all existing hosts are displayed in all capsules, including those that are not managing them


Expected results:

If Host1 is managed by my default (Satellite) capsule, then I should only see information about said host when looking at the default capsule (Capsules page)

If Host1 is managed by an external Capsule1, then I should only see information about said host when looking at Capsule1 and not default capsule


Additional info:

Comment 2 Brad Buckingham 2016-04-18 16:01:12 UTC

The behavior described here appears to be a duplicate of bug 1315416.

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