[
https://issues.apache.org/jira/browse/MESOS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994442#comment-14994442
]
Kapil Arya commented on MESOS-3810:
-----------------------------------
I am seeing the following error with this patch:
{code}
[ RUN ]
LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystemCommandExecutor
+ /local/mesos/mesos.master/build/src/mesos-containerizer mount --help=false
--operation=make-rslave --path=/
+ grep -E
/tmp/LinuxFilesystemIsolatorTest_ROOT_ChangeRootFilesystemCommandExecutor_MtKf0n/.+
/proc/self/mountinfo
+ grep -v 31cd0e88-0dd3-4759-9a24-0550d6ff3495
+ cut '-d ' -f5
+ xargs --no-run-if-empty umount -l
+ mount -n --rbind
/tmp/LinuxFilesystemIsolatorTest_ROOT_ChangeRootFilesystemCommandExecutor_MtKf0n/provisioner/containers/31cd0e88-0dd3-4759-9a24-0550d6ff3495/backends/copy/rootfses/ae3920e6-c5be-4789-b317-5389f4e69171
/tmp/LinuxFilesystemIsolatorTest_ROOT_ChangeRootFilesystemCommandExecutor_MtKf0n/provisioner/containers/31cd0e88-0dd3-4759-9a24-0550d6ff3495/backends/copy/rootfses/78c89388-c7f8-4dac-af2b-7ebef488e1f7/mnt/mesos/sandbox/.rootfs
Changing root to
/tmp/LinuxFilesystemIsolatorTest_ROOT_ChangeRootFilesystemCommandExecutor_MtKf0n/provisioner/containers/31cd0e88-0dd3-4759-9a24-0550d6ff3495/backends/copy/rootfses/78c89388-c7f8-4dac-af2b-7ebef488e1f7
Failed to execute command: No such file or directory
Reached unreachable statement at
../../src/slave/containerizer/mesos/launch.cpp:282
../../src/tests/containerizer/filesystem_isolator_tests.cpp:335: Failure
Value of: statusRunning.get().state()
Actual: TASK_FAILED
Expected: TASK_RUNNING
../../src/tests/containerizer/filesystem_isolator_tests.cpp:336: Failure
Failed to wait 15secs for statusFinished
../../src/tests/containerizer/filesystem_isolator_tests.cpp:330: Failure
Actual function call count doesn't match EXPECT_CALL(sched,
statusUpdate(&driver, _))...
Expected: to be called twice
Actual: called once - unsatisfied and active
*** Aborted at 1446844347 (unix time) try "date -d @1446844347" if you are
using GNU date ***
PC: @ 0x9daae8 mesos::internal::tests::Cluster::Slaves::shutdown()
*** SIGSEGV (@0x7fd300000049) received by PID 22605 (TID 0x7fd39000b8c0) from
PID 73; stack trace: ***
@ 0x7fd38a5d1d60 (unknown)
@ 0x9daae8 mesos::internal::tests::Cluster::Slaves::shutdown()
@ 0xf9dbe2 mesos::internal::tests::MesosTest::ShutdownSlaves()
@ 0xf9dba0 mesos::internal::tests::MesosTest::Shutdown()
@ 0xf9a19d mesos::internal::tests::MesosTest::TearDown()
@ 0x14e548c
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x14e0376
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x14c0cc9 testing::Test::Run()
@ 0x14c1438 testing::TestInfo::Run()
@ 0x14c1a89 testing::TestCase::Run()
@ 0x14c85c7 testing::internal::UnitTestImpl::RunAllTests()
@ 0x14e6153
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x14e0eec
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x14c72a3 testing::UnitTest::Run()
@ 0xdd1688 RUN_ALL_TESTS()
@ 0xdd125a main
@ 0x7fd388562610 __libc_start_main
@ 0x9cf749 _start
@ 0x0 (unknown)
Makefile:8994: recipe for target 'check-local' failed
make[3]: *** [check-local] Segmentation fault (core dumped)
make[3]: Leaving directory '/local/mesos/mesos.master/build/src'
Makefile:8326: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/local/mesos/mesos.master/build/src'
Makefile:8330: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/local/mesos/mesos.master/build/src'
Makefile:682: recipe for target 'check-recursive' failed
make: *** [check-recursive] Error 1
sudo took 30.1146087 seconds
{code}
[~jieyu][~tnachen]: Do you have any pointers on how to debug this?
> Must be able to use NetworkInfo with mesos-executor
> ---------------------------------------------------
>
> Key: MESOS-3810
> URL: https://issues.apache.org/jira/browse/MESOS-3810
> Project: Mesos
> Issue Type: Bug
> Components: containerization, slave
> Affects Versions: 0.25.0
> Reporter: Spike Curtis
> Assignee: Spike Curtis
> Priority: Blocker
>
> ContainerInfo with included NetworkInfo can appear in one of two places
> during a task launch: in the ExecutorInfo.container, or if using the
> mesos-executor (aka command executor), within the TaskInfo.container.
> Mesos 0.25.0 correctly supports the former, but not the latter. In that
> case, the MesosContainerizer fails the task launch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
