You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2017/03/01 17:55:45 UTC

[jira] [Commented] (MESOS-7185) DockerRuntimeIsolatorTest.ROOT_INTERNET_CURL_DockerDefaultEntryptRegistryPuller is flaky

    [ https://issues.apache.org/jira/browse/MESOS-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890675#comment-15890675 ] 

Gilbert Song commented on MESOS-7185:
-------------------------------------

A quick update that I cannot reproduce this issue on my Ubuntu 15.10 box. Will try to triage from the agent log now.

> DockerRuntimeIsolatorTest.ROOT_INTERNET_CURL_DockerDefaultEntryptRegistryPuller is flaky
> ----------------------------------------------------------------------------------------
>
>                 Key: MESOS-7185
>                 URL: https://issues.apache.org/jira/browse/MESOS-7185
>             Project: Mesos
>          Issue Type: Bug
>          Components: test, tests
>    Affects Versions: 1.2.0
>         Environment: Found in 1.2.0-rc2, libevent/SSL enabled, Ubuntu 14.04
>            Reporter: Greg Mann
>              Labels: flaky, flaky-test, mesosphere, test, tests
>         Attachments: DockerDefaultEntryptRegistryPuller.txt
>
>
> Found this while testing 1.2.0-rc2. Libevent/SSL were enabled, and this was on Ubuntu 14.04. The relevant log line seems to be:
> {code}
> E0227 20:42:01.454746 12327 slave.cpp:4650] Container '6f46d724-4927-4e62-9564-51534115a259' for executor '9094c3e3-1cd2-4765-a91a-65f55953b922' of framework 886788e5-5e7e-4918-bb48-b585dd504658-0000 failed to start: Collect failed: Failed to setup hostname and network files: Failed to enter the mount namespace of pid 13138: Failed to open '/proc/13138/ns/mnt': No such file or directory
> {code}
> Find full verbose log attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)