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

UI displays error while switching from detail page of lb service to non-lb service #8460

Closed
zionwu opened this issue Apr 10, 2017 · 2 comments
Assignees
Labels
area/workload internal kind/bug Issues that are defects reported by users or that we know have reached a real release
Milestone

Comments

@zionwu
Copy link
Contributor

zionwu commented Apr 10, 2017

Rancher Versions:
Server: 1.5.3
healthcheck: 0.2.3
ipsec:0.9.4
network-services:0.5.3
scheduler:0.7.5
kubernetes (if applicable):

Docker Version:
Version 17.03.1-ce-mac5

OS and where are the hosts located? (cloud, bare metal, etc):
MacOs

Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher

Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle

Steps to Reproduce:

  1. Go to the service detail page for Load Balance Service, click the second tag "Balancer Rules".
  2. Click the drop down to show other service on the top left corner.
  3. choose another non load balance service.

wechatimg1

Results:
UI display error message as blow:
wechatimg23

@zionwu zionwu changed the title UI display Error while switch from detail page of lb service to other service UI displays Error while switching from detail page of lb service to other service Apr 10, 2017
@zionwu zionwu changed the title UI displays Error while switching from detail page of lb service to other service UI displays error while switching from detail page of lb service to other service Apr 10, 2017
@zionwu zionwu changed the title UI displays error while switching from detail page of lb service to other service UI displays error while switching from detail page of lb service to non-lb service Apr 10, 2017
@tfiduccia
Copy link

Version - master 4/10
This bug exist in master, Error in console:
Application Error TypeError: e.initPorts is not a function route.js:71

@tfiduccia tfiduccia added area/ui kind/bug Issues that are defects reported by users or that we know have reached a real release area/workload labels Apr 10, 2017
@deniseschannon deniseschannon added this to the Release 1.6.0 milestone Apr 21, 2017
@vincent99 vincent99 self-assigned this Apr 25, 2017
@vincent99 vincent99 assigned tfiduccia and unassigned vincent99 Apr 26, 2017
@tfiduccia
Copy link

Version - master 4/26
Verified fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/workload internal 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

4 participants