You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2018/07/26 04:37:00 UTC
[jira] [Commented] (MESOS-8553) Implement a test to reproduce a bug
in launch nested container call.
[ https://issues.apache.org/jira/browse/MESOS-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556888#comment-16556888 ]
Vinod Kone commented on MESOS-8553:
-----------------------------------
Story points?
> Implement a test to reproduce a bug in launch nested container call.
> --------------------------------------------------------------------
>
> Key: MESOS-8553
> URL: https://issues.apache.org/jira/browse/MESOS-8553
> Project: Mesos
> Issue Type: Task
> Components: test
> Reporter: Andrei Budnik
> Assignee: Andrei Budnik
> Priority: Major
> Labels: flaky-test, mesosphere
>
> It's known that in some circumstances an attempt to launch a nested container session might fail with the following error message:
> {code:java}
> Failed to enter mount namespace: Failed to open '/proc/29473/ns/mnt': No such file or directory
> {code}
> That message is written by [linux launcher|https://github.com/apache/mesos/blob/f7dbd29bd9809d1dd254041537ca875e7ea26613/src/slave/containerizer/mesos/launch.cpp#L742-L743] to stdout. This bug is most likely caused by [getMountNamespaceTarget()|https://github.com/apache/mesos/blob/f7dbd29bd9809d1dd254041537ca875e7ea26613/src/slave/containerizer/mesos/utils.cpp#L59].
> Steps for the test could be:
> 1) Start a long running task in its own container (e.g. `sleep 1000`)
> 2) Start a new short-living nested container via `LAUNCH_NESTED_CONTAINER` (e.g. `echo echo`)
> 3) Call `WAIT_NESTED_CONTAINER` on that nested container
> 4) Start long-living nested container via `LAUNCH_NESTED_CONTAINER` (e.g. `cat`)
> 5) Kill that nested container via `KILL_NESTED_CONTAINER`
> 6) Start another long-living nested container via `LAUNCH_NESTED_CONTAINER_SESSION` (e.g. `cat`)
> 7) Attach to the container output via `ATTACH_CONTAINER_OUTPUT`
> 8) Attach to the container input via `ATTACH_CONTAINER_INPUT` and write a non-empty message M to container's stdin
> 9) Check the output of the nested container: it should contain the message M for both `LAUNCH_NESTED_CONTAINER_SESSION` and `ATTACH_CONTAINER_OUTPUT` calls
> The bug might pop up during step 7 or 9.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)