You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2019/05/13 14:27:00 UTC
[jira] [Assigned] (MESOS-8522) `prepareMounts` in Mesos
containerizer is flaky.
[ https://issues.apache.org/jira/browse/MESOS-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bannier reassigned MESOS-8522:
---------------------------------------
Assignee: Gilbert Song (was: Jie Yu)
Assigning to you [~gilbert]. Can we help fixing this?
> `prepareMounts` in Mesos containerizer is flaky.
> ------------------------------------------------
>
> Key: MESOS-8522
> URL: https://issues.apache.org/jira/browse/MESOS-8522
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.5.0
> Reporter: Chun-Hung Hsiao
> Assignee: Gilbert Song
> Priority: Major
> Labels: containerization, mesosphere
>
> The [{{prepareMount()}}|https://github.com/apache/mesos/blob/1.5.x/src/slave/containerizer/mesos/launch.cpp#L244] function in {{src/slave/containerizer/mesos/launch.cpp}} sometimes fails with the following error:
> {noformat}
> Failed to prepare mounts: Failed to mark '/home/docker/containers/af78db6ebc1aff572e576b773d1378121a66bb755ed63b3278e759907e5fe7b6/shm' as slave: Invalid argument
> {noformat}
> The error message comes from https://github.com/apache/mesos/blob/1.5.x/src/slave/containerizer/mesos/launch.cpp#L#L326.
> Although it does not happen frequently, it can be reproduced by running tests that need to clone mount namespaces in repetition. For example, I just reproduced the bug with the following command after 17 minutes:
> {noformat}
> sudo bin/mesos-tests.sh --gtest_filter='*ROOT_PublishResourcesRecovery' --gtest_break_on_failure --gtest_repeat=-1 --verbose
> {noformat}
> No that in this example, the test itself does not involve any docker image or docker containerizer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)