-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
NOMAD_ADDR_* variables incorrect with ipv6 #16550
Labels
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/service-discovery
type/bug
Projects
Comments
Hi @valodzka and thanks for raising this issue. This seems like something we should get fixed up both in the frontend and backend. |
valodzka
pushed a commit
to valodzka/nomad
that referenced
this issue
Mar 30, 2023
valodzka
added a commit
to valodzka/nomad
that referenced
this issue
Apr 6, 2023
valodzka
added a commit
to valodzka/nomad
that referenced
this issue
Apr 20, 2023
I believe the UI problem described has the same root cause as #14654. Refreshing the page should display the service address. |
hc-github-team-nomad-core
added a commit
that referenced
this issue
Apr 21, 2023
…e/1.3.x (#16955) This pull request was automerged via backport-assistant
hc-github-team-nomad-core
added a commit
that referenced
this issue
Apr 21, 2023
…e/1.4.x (#16956) This pull request was automerged via backport-assistant
hc-github-team-nomad-core
added a commit
that referenced
this issue
Apr 21, 2023
…e/1.5.x (#16957) This pull request was automerged via backport-assistant
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/service-discovery
type/bug
Env
nomad 1.5.1, linux node with only ipv6 address
Issue
Nomad env vars have invalid format:
Expected Result
They should be like this:
Related issues
No address for services with IPv6 address in UI:
![image](https://user-images.githubusercontent.com/9821/226107780-5e304193-be2a-4ba2-9552-aab7a7f12781.png)
The text was updated successfully, but these errors were encountered: