-
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
IP/Port info for allocations is missing from UI in 0.12.x #9031
Comments
Good catch, just checked between our 11.3 and 12.5 cluster and I can confirm the 'Addresses' column is missing on the allocation details page |
Hey @gmichalec-pandora If you define your ports as part of the group then they will appear as part of the alloc info page in a separate "Ports" table. I'm going to keep this open as I plan to to try and expose the deprecated task network ports into this table to try and ease the confusion here. |
Thanks for responding - I updated a job to use the new syntax and indeed the port info showed up. However, until #8780 is resolved, it's going to be a huge undertaking to get our 100s of users to update 1000s of job specs to use the new syntax - currently it seems to require not only moving the network definition, but also any service definitions that use port labels. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
For reporting security vulnerabilities please refer to the website.
If you have a question, prepend your issue with
[question]
or preferably use the nomad mailing list.If filing a bug please include the following:
Nomad version
0.12.5-ent
Operating system and Environment details
Debian Buster
Issue
After upgrading from 0.11.3 -> 0.12.5, we noticed that the allocation/task view in the UI no longer lists the IP/Port of allocations.
It appears to be related to this commit - https://github.com/hashicorp/nomad/pull/8631/files
Reproduction steps
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: