[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Updated] (MESOS-4812) Mesos fails to escape command health checks
From:       "Michael Park (JIRA)" <jira () apache ! org>
Date:       2017-06-29 22:48:00
Message-ID: JIRA.12945534.1456767995000.139632.1498776480291 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/MESOS-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Michael Park updated MESOS-4812:
--------------------------------
    Shepherd: Alexander Rukletsov

> 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: haosdent
> Labels: health-check, mesosphere
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]