Bug 1327700 - Capsules should only show information about hosts that are associated with it
Summary: Capsules should only show information about hosts that are associated with it
Keywords:
Status: CLOSED DUPLICATE of bug 1315416
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Shlomi Zadok
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 16:10 UTC by Og Maciel
Modified: 2019-04-01 20:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-18 16:01:12 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.