Bug 1311766

Summary: Cockpit filter option not filtering out project specific details
Product: Red Hat Enterprise Linux 7 Reporter: Eric Jones <erjones>
Component: cockpitAssignee: Peter <pvolpe>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: aos-bugs, dperpeet, erjones, jokerman, mmccomas
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Atomic Enterprise Platform
Last Closed: 2016-11-10 16:29:45 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:
Attachments:
Description Flags
Example of specifying different project and still seeing default services none

Description Eric Jones 2016-02-24 23:14:24 UTC 
Description of problem:
Customer indicated that he is able to see services and other details that are specific to one project/namespace while filtering on for a different project/namespace.

Version-Release number of selected component (if applicable):
Customer just upgraded cockpit to 0.93

How reproducible:
100% for the customer

Steps to Reproduce:
1. Identify a service (like kubernetes) in the default project
2. Change the "Project" filter in the top left corner of the screen to a different project

Actual results:
Still see the same service (like kubernetes) while "filtering" for a different project

Expected results:
Only see services for the project you are "filtering" for.
Comment 1 Eric Jones 2016-02-24 23:15:12 UTC 
Created attachment 1130362 [details]
Example of specifying different project and still seeing default services
Comment 2 Andy Goldstein 2016-02-24 23:17:44 UTC 
Shouldn't this be filed under RHEL7/cockpit?
Comment 3 Eric Jones 2016-02-24 23:23:15 UTC 
Yes, yes it should. Sorry Andy.
Comment 5 Peter 2016-04-27 13:32:17 UTC 
I'm not able to reproduce, on either the current release (0.103) or 0.93. Quite a bit has changed between those two versions including the way the filter works. If you are able to reproduce on 0.103, it is only the topology view that has this bug?  Does the problem happen with other services than the default kubernetes one? what about other namespaces?
Comment 8 Dominik Perpeet 2016-11-10 16:29:45 UTC 
Filtering should work correctly in the current release, as Peter said significant work has been done there. Please open a new bug if this happens on a newer version.