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

Wrong host labels on container nodes #1501

Closed
2opremio opened this issue May 12, 2016 · 6 comments
Closed

Wrong host labels on container nodes #1501

2opremio opened this issue May 12, 2016 · 6 comments
Assignees
@tomwilkie
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone
0.15.0

Comments

@2opremio
Copy link
Contributor

2opremio commented May 12, 2016 •
edited
Loading

screen shot 2016-05-12 at 7 39 51 pm

Note how the container node label reads ip-172-31-0-5 (in fact all containers do) but the details panel shows (correctly) ip-172-31-0-6

I believe this is a regression (it at least worked on 0.13.1, see the screenshots at #1162 )

Tentatively marked as ui bug
@2opremio 2opremio added bug Broken end user or developer functionality; not working as the developers intended it component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer labels May 12, 2016
@2opremio 2opremio added this to the 0.15.0 milestone May 12, 2016
@2opremio
Copy link
Contributor Author

Report: report_wrong_node_labels.json.gz

@tomwilkie tomwilkie self-assigned this May 13, 2016
@tomwilkie tomwilkie removed the component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer label May 13, 2016
@tomwilkie
Copy link
Contributor

I don't think its the UI, as the events from the backend have the wrong labels.

@tomwilkie
Copy link
Contributor

Yeah, in fact if you hit a node endpoint and refresh, you get two different hostnames.

@tomwilkie
Copy link
Contributor

This definitely doesn't affect the process topology.

@tomwilkie
Copy link
Contributor

And has nothing to do with k8s.

@tomwilkie tomwilkie mentioned this issue May 13, 2016
Merged
@2opremio
Copy link
Contributor Author

And has nothing to do with k8s.

This is ECS

@tomwilkie tomwilkie mentioned this issue May 16, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomwilkie tomwilkie

Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Milestone
0.15.0
Development

No branches or pull requests
2 participants
@tomwilkie @2opremio