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.

Sign up for GitHub

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

Jump to bottom

Cloning of LB services created from API fails #1973

Closed
sangeethah opened this issue Sep 4, 2015 · 5 comments
Closed

Cloning of LB services created from API fails #1973

sangeethah opened this issue Sep 4, 2015 · 5 comments
Assignees
@deniseschannon
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release
Milestone
Milestone 10/7/2015

Comments

@sangeethah
Copy link
Contributor

Sever version - Build from master - Sep 4

Had a LB service with ssl enabled listener and certs.

screen shot 2015-09-04 at 10 21 11 am

Tried to clone this LB service . I get redirected to /static/fail page with following contents:

Error
Cannot read property 'set' of null
Reload to try again or log out
@sangeethah sangeethah added kind/bug Issues that are defects reported by users or that we know have reached a real release area/ui labels Sep 4, 2015
@sangeethah sangeethah added this to the Milestone 9/2/2015 milestone Sep 4, 2015
@vincent99
Copy link
Contributor

works for me... can I see this one somewhere?

@sangeethah sangeethah removed this from the Milestone 9/2/2015 milestone Sep 8, 2015
@sangeethah
Copy link
Contributor Author

This issue is not reproducible when LB instance is created using UI.
I am able to see this issue when i used API calls to create LB services.

@andrefreitas andrefreitas mentioned this issue Sep 17, 2015
Closed
@deniseschannon deniseschannon changed the title Cloning of LB services with ssl enabled listener and certs redirects to /static/fail page. Cloning of LB services created from API fails Sep 22, 2015
@deniseschannon deniseschannon added this to the Milestone 9/23/2015 milestone Sep 22, 2015
@deniseschannon
Copy link

@vincent99 Can you look at #2059 because I believe it's the same issue but his use case is simpler. Basically, any LB created using API seems to fail when cloning.

This is probably a duplicate of #1700 that we ended up closing cause we couldn't reproduce.

@vincent99
Copy link
Contributor

This was caused by balancers created with rancher-compose not having a loadBalancerConfig object in them (for stickiness options and such).

vincent99 added a commit to vincent99/ui that referenced this issue Oct 8, 2015
@vincent99
Fix balancer clone with no loadBalancerConfig (rancher/rancher#1973)
0e72cd7
vincent99 added a commit to rancher/ui that referenced this issue Oct 8, 2015
@vincent99
Merge pull request #273 from vincent99/master
e778cd5 
Fix balancer clone with no loadBalancerConfig (rancher/rancher#1973)
@vincent99 vincent99 assigned deniseschannon and unassigned vincent99 Oct 9, 2015
@deniseschannon
Copy link

Verified in v0.41.0-rc1 using rancher-compose to create a LB. Cloning the LB has no issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@deniseschannon deniseschannon

Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Milestone
Milestone 10/7/2015
Development

No branches or pull requests
4 participants
@vincent99 @sangeethah @will-chan @deniseschannon