mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-3379) LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint is failed
Date Sat, 16 Jan 2016 08:46:39 GMT

     [ https://issues.apache.org/jira/browse/MESOS-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Chen updated MESOS-3379:
--------------------------------
    Fix Version/s: 0.27.0

> 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
>             Fix For: 0.27.0
>
>
> {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)

Mime
View raw message