[
https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946560#comment-14946560
]
haosdent edited comment on MESOS-3136 at 10/7/15 9:17 AM:
----------------------------------------------------------
I remember should be {noformat}--launcher_dir={noformat} not
{noformat}--launch-dir{noformat}. you missing {noformat}er{noformat} and use
wrong {noformat}-{noformat}. And if you think running health check outside
docker container is necessary, please feel free to open a new ticket as adam
said. If that issue is acceptted, I would submit a patch for that as soon as
possible.
was (Author: [email protected]):
I remember should be "--launcher_dir=" not "--launch-dir". you missing "er" and
use wrong "-".
> COMMAND health checks with Marathon 0.10.0 are broken
> -----------------------------------------------------
>
> Key: MESOS-3136
> URL: https://issues.apache.org/jira/browse/MESOS-3136
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Dr. Stefan Schimanski
> Assignee: haosdent
> Priority: Critical
> Fix For: 0.23.1, 0.24.1, 0.25.0
>
> Attachments: MESOS-3136_0_23_0.patch, MESOS-3136_0_24_0.patch
>
>
> When deploying Mesos 0.23rc4 with latest Marathon 0.10.0 RC3 command health
> check stop working. Rolling back to Mesos 0.22.1 fixes the problem.
> Containerizer is Docker.
> All packages are from official Mesosphere Ubuntu 14.04 sources.
> The issue must be analyzed further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
