You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/09/07 20:19:45 UTC
[jira] [Assigned] (MESOS-3379)
LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint is failed
[ https://issues.apache.org/jira/browse/MESOS-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
haosdent reassigned MESOS-3379:
-------------------------------
Assignee: haosdent
> LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint is failed
> --------------------------------------------------------------------------
>
> Key: MESOS-3379
> URL: https://issues.apache.org/jira/browse/MESOS-3379
> Project: Mesos
> Issue Type: Bug
> Reporter: haosdent
> Assignee: haosdent
> Labels: flaky-test
>
> {code}
> sudo GLOG_v=1 ./bin/mesos-tests.sh --gtest_filter="LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint" --verbose
> {code}
> failed in Ubuntu 14.04
> Just a problem when investing [MESOS-3349 PersistentVolumeTest.AccessPersistentVolume fails when run as root.|https://issues.apache.org/jira/browse/MESOS-3349]
> In LinuxFilesystemIsolatorProcess::cleanup, when we read mount table and umount. The order should use reverse order. Suppose our mount order is
> {code}
> mount /tmp/a /tmp/b
> mount /tmp/c /tmp/b/c
> {code}
> Currently we umount logic in cleanup is
> {code}
> umount /tmp/b
> umount /tmp/b/c <- Wrong
> {code}
> This is the reason why ROOT_VolumeFromHostSandboxMountPoint failed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)