-
Notifications
You must be signed in to change notification settings - Fork 845
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
Ports values were swapped in the UI based on Mesos data #4781
Comments
it sounds like this is a DCOS UI bug vs. a Marathon bug |
I think the data source for this display is the groups api (the UI always use the groups endpoint) inside the nodes under |
Talked to @lloesche, he said that this happens only for resident tasks and this was an ui issue. The api worked as expected. I tried to reproduce this with current testing/master cluster but it did not happen within 20 restarts. |
With the following app definition this behavior is reproducible:
UI:
Docker deamon:
|
Ok, investigated again: Marathon re-uses TaskIds for resident Tasks, this means that the mesos state.json will return something like this:
and when the users clicks on a particular task in the ui, the ui tries to request the information for the task with the id |
copy of https://mesosphere.atlassian.net/browse/DCOS-9629
reported by @lloesche
I have a service that uses persistent volumes and two tcp ports.
When restarting the service it's being restarted on the same host using the same random host ports. However the mapping of container to host port might be shuffled.
E.g.
container 9090 -> host 21926
container 9093 -> host 21927
RESTART
container 9090 -> host 21927
container 9093 -> host 21926
However the DC/OS UI shows the host to container port mapping wrong every now and then.
![screen shot 2016-09-06 at 19 04 13](https://cloud.githubusercontent.com/assets/19775099/20927457/fa0398f4-bbc1-11e6-98a1-575ee448375e.png)
It's correct after initial start but sometimes incorrect after the ports have been shuffled due to a restart.
state.json.txt
Example /service/marathon/v2/apps/prometheus/server output fetched when the screenshot above was taken.
The Load balancer UI shows the correct mapping btw. it's only the Service view that doesn't
The text was updated successfully, but these errors were encountered: