[
https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644126#comment-14644126
]
Adam B commented on MESOS-3136:
-------------------------------
No. Mesos 0.23.0 was released the day before this issue was filed. We could
package the fix into a 0.23.1 if it's critical.
However, now that we're moving towards a monthly release cycle, we plan to cut
a 0.24.0 release candidate (rc1) soon (next week?), so it might make more sense
to just focus on getting somebody to fix this before 0.24.0-rc1 comes out.
(Adding some metadata in hopes that this'll get more attention.)
> COMMAND health checks with Marathon 0.10.0rc3 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
>
> 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)