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 Link to nodePort host always %3Cnil%3E #15482

Closed
stefanvangastel opened this Issue Sep 10, 2018 · 2 comments

Comments

Projects
None yet
5 participants
@stefanvangastel

stefanvangastel commented Sep 10, 2018

Rancher versions:
Rancher: v2.0.8
User Interface: v2.0.67
Helm: v2.9.1-rancher1
Machine: v0.15.0-rancher1-1

Infrastructure Stack versions:
kubectl version

Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:17:28Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"windows/amd64"}

Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

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

Steps to Reproduce:
Add new scalable deployment to Rancher 2.0.8 using nodePort portmapping. Hover link to exposed port. This shows (and opens) e.g. %3Cnil%3E:30297

Results:
nil

@westlywright

This comment has been minimized.

Show comment
Hide comment
@westlywright

westlywright Sep 10, 2018

Member

QA: I am no longer seeing this in the 2.1 dev branch. I think the issue may have been resolved. Can we verify this? If the issue does persist I have a sneaking suspicion that the issue is on the back end. That link is retrieved from the node's public endpoints and we do not use <nil> on the front end. I think we possibly had some string included when it should not have been.

Member

westlywright commented Sep 10, 2018

QA: I am no longer seeing this in the 2.1 dev branch. I think the issue may have been resolved. Can we verify this? If the issue does persist I have a sneaking suspicion that the issue is on the back end. That link is retrieved from the node's public endpoints and we do not use <nil> on the front end. I think we possibly had some string included when it should not have been.

@tfiduccia

This comment has been minimized.

Show comment
Hide comment
@tfiduccia

tfiduccia Sep 10, 2018

@stefanvangastel - I cannot reproduce this. So I'm closing, if you can reproduce after next release just re-open.

tfiduccia commented Sep 10, 2018

@stefanvangastel - I cannot reproduce this. So I'm closing, if you can reproduce after next release just re-open.

@tfiduccia tfiduccia closed this Sep 10, 2018

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