[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946594#comment-14946594 ] Erhan Kesken commented on MESOS-3136: - I cloned this issue as adam suggested: MESOS-35

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946570#comment-14946570 ] Erhan Kesken commented on MESOS-3136: - sorry for my lack of attention, I had used para

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946563#comment-14946563 ] Erhan Kesken commented on MESOS-3136: - as you stated, I think both option is required,

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946560#comment-14946560 ] haosdent commented on MESOS-3136: - I remember should be "--launcher_dir=" not "--launch-di

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946545#comment-14946545 ] Erhan Kesken commented on MESOS-3136: - both mesos-docker-executor and mesos-health-che

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946490#comment-14946490 ] Adam B commented on MESOS-3136: --- I can understand the desire to run in the docker, so that i

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946456#comment-14946456 ] haosdent commented on MESOS-3136: - You need set MESOS_LAUNCHER_DIR or make sure mesos-dock

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946444#comment-14946444 ] haosdent commented on MESOS-3136: - A bit confuse, should the health check running outside

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946393#comment-14946393 ] Erhan Kesken commented on MESOS-3136: - I tested mesos 0.24.1 with marathon 0.11.0, I'm

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946378#comment-14946378 ] Erhan Kesken commented on MESOS-3136: - Issue is marked as resolved, but from line htt

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791092#comment-14791092 ] Timothy Chen commented on MESOS-3136: - commit 5d6a06082ce396582add2e3e8497e1f4cdf91ec1

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744933#comment-14744933 ] Adam B commented on MESOS-3136: --- [~greggomann] is doing some (internal) backport testing for

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743799#comment-14743799 ] haosdent commented on MESOS-3136: - Do you have a link to [~greggomann]'s work? I could not

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743728#comment-14743728 ] Marco Massenzio commented on MESOS-3136: I'm wondering how does this relate to the

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743080#comment-14743080 ] haosdent commented on MESOS-3136: - [~marco-mesos][~adam-mesos][~tnachen] If we could backp

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728400#comment-14728400 ] Evan Krall commented on MESOS-3136: --- We also have Marathon jobs that are relying on comm

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727918#comment-14727918 ] Vinod Kone commented on MESOS-3136: --- I'm afraid not considering this is not new in 24.0

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727849#comment-14727849 ] Casey Sybrandy commented on MESOS-3136: --- I'm seeing this issue as well. Is there a

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700440#comment-14700440 ] Marco Massenzio commented on MESOS-3136: [~vinodkone] does this need to be fixed b

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700438#comment-14700438 ] Marco Massenzio commented on MESOS-3136: Just noticed this entirely randomly... I

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644188#comment-14644188 ] Adam B commented on MESOS-3136: --- We generally don't support skipping a version in a live rol

[jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken

[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644157#comment-14644157 ] haosdent commented on MESOS-3136: - If 0.22 users could upgrade to 0.24 directly? > COMMAN