You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2017/11/02 18:40:00 UTC
[jira] [Updated] (MESOS-4812) Mesos fails to escape command health
checks
[ https://issues.apache.org/jira/browse/MESOS-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Rukletsov updated MESOS-4812:
---------------------------------------
Sprint: Mesosphere Sprint 65, Mesosphere Sprint 66 (was: Mesosphere Sprint 65, Mesosphere Sprint 66, Mesosphere Sprint 67)
> Mesos fails to escape command health checks
> -------------------------------------------
>
> Key: MESOS-4812
> URL: https://issues.apache.org/jira/browse/MESOS-4812
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.25.0
> Reporter: Lukas Loesche
> Assignee: Andrei Budnik
> Priority: Major
> Labels: health-check, mesosphere, tech-debt
> Attachments: health_task.gif
>
>
> As described in https://github.com/mesosphere/marathon/issues/3333
> I would like to run a command health check
> {noformat}
> /bin/bash -c "</dev/tcp/$HOST/$PORT0"
> {noformat}
> The health check fails because Mesos, while running the command inside double quotes of a sh -c "" doesn't escape the double quotes in the command.
> If I escape the double quotes myself the command health check succeeds. But this would mean that the user needs intimate knowledge of how Mesos executes his commands which can't be right.
> I was told this is not a Marathon but a Mesos issue so am opening this JIRA. I don't know if this only affects the command health check.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)