[
https://issues.apache.org/jira/browse/MESOS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728161#comment-14728161
]
Greg Mann commented on MESOS-3349:
----------------------------------
This output from Ubuntu 14:
{code}
I0902 22:09:26.596101 31762 linux.cpp:493] Removing mount
'/tmp/PersistentVolumeTest_AccessPersistentVolume_9Q2Zk1/slaves/20150902-220926-251789322-39756-31742-S0/frameworks/20150902-220926-251789322-39756-31742-0000/executors/d89c6891-f9c4-4de9-b8ea-f75d0f4fe754/runs/ff43a3f9-fd1c-4923-8640-e3eed2744d5d/path1'
for persistent volume disk(role1)[id1:path1]:64 of container
ff43a3f9-fd1c-4923-8640-e3eed2744d5d
I0902 22:09:26.596161 31759 process.cpp:2410] Resuming (10)@10.0.2.15:39756 at
2015-09-02 22:09:26.596153856+00:00
I0902 22:09:26.596191 31759 process.cpp:2410] Resuming (11)@10.0.2.15:39756 at
2015-09-02 22:09:26.596188160+00:00
I0902 22:09:26.596211 31759 process.cpp:2410] Resuming __gc__@10.0.2.15:39756
at 2015-09-02 22:09:26.596208128+00:00
I0902 22:09:26.596267 31759 process.cpp:2410] Resuming (24)@10.0.2.15:39756 at
2015-09-02 22:09:26.596262912+00:00
I0902 22:09:26.605408 31762 process.cpp:2410] Resuming (24)@10.0.2.15:39756 at
2015-09-02 22:09:26.605393920+00:00
I0902 22:09:26.605957 31762 process.cpp:2515] Cleaning up (24)@10.0.2.15:39756
I0902 22:09:26.606415 31762 process.cpp:2410] Resuming __gc__@10.0.2.15:39756
at 2015-09-02 22:09:26.606408960+00:00
I0902 22:09:26.606077 31757 process.cpp:2410] Resuming slave(1)@10.0.2.15:39756
at 2015-09-02 22:09:26.606065920+00:00
E0902 22:09:26.607035 31757 slave.cpp:2870] Failed to update resources for
container ff43a3f9-fd1c-4923-8640-e3eed2744d5d of executor
d89c6891-f9c4-4de9-b8ea-f75d0f4fe754 running task
d89c6891-f9c4-4de9-b8ea-f75d0f4fe754 on status update for terminal task,
destroying container: Collect failed: Failed to remove persistent volume mount
point at
'/tmp/PersistentVolumeTest_AccessPersistentVolume_9Q2Zk1/slaves/20150902-220926-251789322-39756-31742-S0/frameworks/20150902-220926-251789322-39756-31742-0000/executors/d89c6891-f9c4-4de9-b8ea-f75d0f4fe754/runs/ff43a3f9-fd1c-4923-8640-e3eed2744d5d/path1':
Device or resource busy
{code}
vs. this output from OSX:
{code}
I0902 15:18:19.899541 197115904 posix.cpp:156] Removing symlink
'/tmp/PersistentVolumeTest_AccessPersistentVolume_ZPXsHo/slaves/20150902-151819-1229914122-63371-94565-S0/frameworks/20150902-151819-1229914122-63371-94565-0000/executors/e5421321-94ed-4495-9b1d-3f3aed9bb522/runs/d903841d-f1da-46e6-ab05-eb437ac9e4e8/path1'
for persistent volume disk(role1)[id1:path1]:64 of container
d903841d-f1da-46e6-ab05-eb437ac9e4e8
{code}
So it seems the persistent volume is still in use by the executor at the time
it's unmounted, but since a symlink is used on OSX it succeeds anyway.
> PersistentVolumeTest.AccessPersistentVolume fails when run as root.
> -------------------------------------------------------------------
>
> Key: MESOS-3349
> URL: https://issues.apache.org/jira/browse/MESOS-3349
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: Ubuntu 14.04, CentOS 5
> Reporter: Benjamin Mahler
> Labels: flaky-test
>
> When running the tests as root:
> {noformat}
> [ RUN ] PersistentVolumeTest.AccessPersistentVolume
> I0901 02:17:26.435140 39432 exec.cpp:133] Version: 0.25.0
> I0901 02:17:26.442129 39461 exec.cpp:207] Executor registered on slave
> 20150901-021726-1828659978-52102-32604-S0
> Registered executor on hostname
> Starting task d8ff1f00-e720-4a61-b440-e111009dfdc3
> sh -c 'echo abc > path1/file'
> Forked command at 39484
> Command exited with status 0 (pid: 39484)
> ../../src/tests/persistent_volume_tests.cpp:579: Failure
> Value of: os::exists(path::join(directory, "path1"))
> Actual: true
> Expected: false
> [ FAILED ] PersistentVolumeTest.AccessPersistentVolume (777 ms)
> {noformat}
> FYI [~jieyu] [~mcypark]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
