Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

K8s - UI - pods from across namespace gets listed in services pages. #5976

Closed
sangeethah opened this issue Sep 14, 2016 · 1 comment
Closed
Assignees
Labels
area/kubernetes kind/bug Issues that are defects reported by users or that we know have reached a real release
Milestone

Comments

@sangeethah
Copy link
Contributor

sangeethah commented Sep 14, 2016

Server version - v1.1.4-rc1
K8s template from https://github.com/rancher/qa-catalog.

Steps to reproduce the problem:
Create namespace test1.
Create services/pods/ingress in this namespace.
Create namespace test2.
Create the same set of services/pods/ingress as test1 in test2.

Services list view for test1 list the pods from services of the same name that belong to namespace test2 .

Same behavior is also seen with service in test2.
screen shot 2016-09-14 at 2 15 16 pm

> kubectl get pods --namespace test1
NAME            READY     STATUS    RESTARTS   AGE
k8test7-4y4jz   1/1       Running   0          50m
k8test7-51yk9   1/1       Running   0          50m
> kubectl get pods --namespace test2
NAME            READY     STATUS    RESTARTS   AGE
k8test7-2l33b   1/1       Running   0          50m
k8test7-jny8a   1/1       Running   0          50m
> kubectl get pods --namespace test3
> kubectl get pods
NAME            READY     STATUS    RESTARTS   AGE
k8test5-2h6em   1/1       Running   0          2h
k8test5-jcpsl   1/1       Running   0          2h
k8test6-ckulj   1/1       Running   0          1h
k8test6-wsywc   1/1       Running   0          1h
k8test7-emvlq   1/1       Running   0          1h
k8test7-le22j   1/1       Running   0          1h
@sangeethah sangeethah added the kind/bug Issues that are defects reported by users or that we know have reached a real release label Sep 14, 2016
@sangeethah sangeethah added this to the 1.1.4 milestone Sep 14, 2016
vincent99 added a commit to rancher/ui that referenced this issue Sep 14, 2016
@sangeethah
Copy link
Contributor Author

This issue is not reproducible using rancher server version - v1.1.4-rc2

been2io pushed a commit to been2io/ui that referenced this issue Oct 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubernetes kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

3 participants