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

cli: alloc status Task Resources malformed when listing multiple addresses #8161

Closed
jrasell opened this issue Jun 15, 2020 · 1 comment · Fixed by #8162
Closed

cli: alloc status Task Resources malformed when listing multiple addresses #8161

jrasell opened this issue Jun 15, 2020 · 1 comment · Fixed by #8162
Assignees
Milestone

Comments

@jrasell
Copy link
Member

jrasell commented Jun 15, 2020

Nomad version

Master commit: 723437f87e53b1d21b2e3442bdc4e401755ce891

Operating system and Environment details

Reproduced on MacOS

Issue

When performing nomad alloc status on an allocation within a task group that is configured with more than one resources.network.port, the output is malformed as shown below:

Task Resources
CPU        Memory          Disk     Addresses
9/200 MHz  12 MiB/256 MiB  300 MiB  api: 172.31.8.253:8081
                                                            grafana: 172.31.8.253:3000
                                                            prometheus: 172.31.8.253:9090
                                                            webapp: 172.31.8.253:80
@github-actions
Copy link

github-actions bot commented Nov 6, 2022

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant