mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kang (JIRA)" <>
Subject [jira] [Commented] (MESOS-6485) task launched and lost management after task failed
Date Thu, 01 Dec 2016 04:34:58 GMT


Daniel Kang commented on MESOS-6485:

i don't think so. if "ro" makes it failed, it should be always failed. Meanwhile, it failed

> task launched and lost management after task failed
> ---------------------------------------------------
>                 Key: MESOS-6485
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker, framework
>    Affects Versions: 1.0.1
>            Reporter: Daniel Kang
>            Assignee: haosdent
>         Attachments: agent-log.txt, master-log.txt, stderr.txt, stdout.txt
> i used marathon+mesos to launch my apps.
> when i update my app's image configuration and deploy it, i found a task failed, and
then a new task is launched. Meanwhile, i use "docker ps" to get all containers, i found the
failed task was launched, and the status of this task in mesos is failed and completed.
> mesos lost the management for this failed task. 
> is this a bug?
> steps to reproduce:
> 1. update image configuration, and redploy
> 2. make sure image be pulled after a long time
> logs for this:
> State
> Message
> Failed to launch container: Failed to run 'docker -H unix:///var/run/docker.sock inspect
mesos-f82fd98b-ba99-4ffe-bab5-eaa9dab8d5cc-S1.d84d9d59-218d-47fd-b930-e0d2359e61fa': exited
with status 1; stderr='Error: No such image, container or task: mesos-f82fd98b-ba99-4ffe-bab5-eaa9dab8d5cc-S1.d84d9d59-218d-47fd-b930-e0d2359e61fa
> docker ps | grep mesos-f82fd98b-ba99-4ffe-bab5-eaa9dab8d5cc-S1.d84d9d59-218d-47fd-b930-e0d2359e61fa

This message was sent by Atlassian JIRA

View raw message