[jira] [Commented] (MESOS-5770) Mesos state api reporting Host IP instead of container IP with health check
[ https://issues.apache.org/jira/browse/MESOS-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383248#comment-15383248 ] Lax commented on MESOS-5770: You can mark it resolved now. Have tried out the fix (https://github.com/apache/mesos/commit/cca92ceac75c7639c4ae93660b3bb15cce11c5c3) and it works. Now I can learn container IP with health check on too - Thanks > Mesos state api reporting Host IP instead of container IP with health check > > > Key: MESOS-5770 > URL: https://issues.apache.org/jira/browse/MESOS-5770 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Priority: Critical > Fix For: 0.28.0 > > > Am using Mesos IP per container using docker containerizer (via Calico). > Mesos state API (/master/state.json) seems to report container IP as long as > I have no health check on my task. As soon as I add health check to the task, > mesos start reporting Host IP instead of Container IP. > Had initially opened this bug on Marathon > (https://github.com/mesosphere/marathon/issues/3907). But then told the issue > is with Mesos reporting the wrong IP. > Here are versions of Mesos and Marathon I was using. > Mesos: 0.28.0.2 > Marathon: 0.15.3-1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5770) Mesos state api reporting Host IP instead of container IP with health check
[ https://issues.apache.org/jira/browse/MESOS-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366368#comment-15366368 ] Lax commented on MESOS-5770: Between I tried packaging the latest code base still see the issue. Any pointers on where I can start digging up while you are also looking into it. We badly need this resolved for us to move forward. > Mesos state api reporting Host IP instead of container IP with health check > > > Key: MESOS-5770 > URL: https://issues.apache.org/jira/browse/MESOS-5770 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Priority: Critical > Fix For: 0.28.0 > > > Am using Mesos IP per container using docker containerizer (via Calico). > Mesos state API (/master/state.json) seems to report container IP as long as > I have no health check on my task. As soon as I add health check to the task, > mesos start reporting Host IP instead of Container IP. > Had initially opened this bug on Marathon > (https://github.com/mesosphere/marathon/issues/3907). But then told the issue > is with Mesos reporting the wrong IP. > Here are versions of Mesos and Marathon I was using. > Mesos: 0.28.0.2 > Marathon: 0.15.3-1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5770) Mesos state api reporting Host IP instead of container IP with health check
[ https://issues.apache.org/jira/browse/MESOS-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362862#comment-15362862 ] Lax commented on MESOS-5770: Ok, thanks haosdent. > Mesos state api reporting Host IP instead of container IP with health check > > > Key: MESOS-5770 > URL: https://issues.apache.org/jira/browse/MESOS-5770 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Priority: Critical > Fix For: 0.28.0 > > > Am using Mesos IP per container using docker containerizer (via Calico). > Mesos state API (/master/state.json) seems to report container IP as long as > I have no health check on my task. As soon as I add health check to the task, > mesos start reporting Host IP instead of Container IP. > Had initially opened this bug on Marathon > (https://github.com/mesosphere/marathon/issues/3907). But then told the issue > is with Mesos reporting the wrong IP. > Here are versions of Mesos and Marathon I was using. > Mesos: 0.28.0.2 > Marathon: 0.15.3-1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5770) Mesos state api reporting Host IP instead of container IP with health check
[ https://issues.apache.org/jira/browse/MESOS-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362836#comment-15362836 ] haosdent commented on MESOS-5770: - Hi, for the package of mesos, you could refer to https://github.com/mesosphere/mesos-deb-packaging and https://github.com/apache/mesos/blob/master/docs/getting-started.md#system-requirements And I would start to investigate the root cause tomorrow, would inform you if have any progress. Thank you for your helps again. > Mesos state api reporting Host IP instead of container IP with health check > > > Key: MESOS-5770 > URL: https://issues.apache.org/jira/browse/MESOS-5770 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Priority: Critical > Fix For: 0.28.0 > > > Am using Mesos IP per container using docker containerizer (via Calico). > Mesos state API (/master/state.json) seems to report container IP as long as > I have no health check on my task. As soon as I add health check to the task, > mesos start reporting Host IP instead of Container IP. > Had initially opened this bug on Marathon > (https://github.com/mesosphere/marathon/issues/3907). But then told the issue > is with Mesos reporting the wrong IP. > Here are versions of Mesos and Marathon I was using. > Mesos: 0.28.0.2 > Marathon: 0.15.3-1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5770) Mesos state api reporting Host IP instead of container IP with health check
[ https://issues.apache.org/jira/browse/MESOS-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362755#comment-15362755 ] Lax commented on MESOS-5770: Is the work around suggested in other ticket good to be picked up? If so, is there a way to build packaged version of mesos? would like to package mesos and try out the patch. > Mesos state api reporting Host IP instead of container IP with health check > > > Key: MESOS-5770 > URL: https://issues.apache.org/jira/browse/MESOS-5770 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Priority: Critical > Fix For: 0.28.0 > > > Am using Mesos IP per container using docker containerizer (via Calico). > Mesos state API (/master/state.json) seems to report container IP as long as > I have no health check on my task. As soon as I add health check to the task, > mesos start reporting Host IP instead of Container IP. > Had initially opened this bug on Marathon > (https://github.com/mesosphere/marathon/issues/3907). But then told the issue > is with Mesos reporting the wrong IP. > Here are versions of Mesos and Marathon I was using. > Mesos: 0.28.0.2 > Marathon: 0.15.3-1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5770) Mesos state api reporting Host IP instead of container IP with health check
[ https://issues.apache.org/jira/browse/MESOS-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360790#comment-15360790 ] haosdent commented on MESOS-5770: - Hi, [~lax77] Thank you for your report. This is duplicated with MESOS-5294. > Mesos state api reporting Host IP instead of container IP with health check > > > Key: MESOS-5770 > URL: https://issues.apache.org/jira/browse/MESOS-5770 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Priority: Critical > Fix For: 0.28.0 > > > Am using Mesos IP per container using docker containerizer (via Calico). > Mesos state API (/master/state.json) seems to report container IP as long as > I have no health check on my task. As soon as I add health check to the task, > mesos start reporting Host IP instead of Container IP. > Had initially opened this bug on Marathon > (https://github.com/mesosphere/marathon/issues/3907). But then told the issue > is with Mesos reporting the wrong IP. > Here are versions of Mesos and Marathon I was using. > Mesos: 0.28.0.2 > Marathon: 0.15.3-1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
