Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Duplicate
-
1.4.1
-
None
-
Containerization: RI13 Sp 45
-
1
Description
I was deploying an application through marathon in an integration test that looked like this:
- Mesos container (UCR)
- container network
- some network name specified
Given network name did not exist, I did not even passed CNI config to the agent.
After Mesos tried to deploy my task, the agent crashed because of missing CNI config.
[31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] *** SIGABRT (@0x1980) received by PID 6528 (TID 0x7f3124b58700) from PID 6528; stack trace: *** [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f312e5c2890 (unknown) [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f312e23d067 (unknown) [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f312e23e448 (unknown) [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f312e236266 (unknown) [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f312e236312 (unknown) [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f31304fd233 _ZNKR6OptionISsE3getEv.part.103 [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f313050b60c mesos::internal::slave::NetworkCniIsolatorProcess::getNetworkConfigJSON() [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f313050bd54 mesos::internal::slave::NetworkCniIsolatorProcess::prepare() [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f313027b903 _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEESt5_BindIFZNS0_8dispatchI6OptionIN5mesos5slave19ContainerLaunchInfoEENS7_8internal5slave20MesosIsolatorProcessERKNS7_11ContainerIDERKNS8_15ContainerConfigESG_SJ_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSO_FSM_T1_T2_EOT3_OT4_EUlRSE_RSH_S2_E_SE_SH_St12_PlaceholderILi1EEEEE9_M_invokeERKSt9_Any_dataS2_ [31mWARN [0;39m[10:51:53 AppDeployIntegrationTest-MesosAgent-32780] @ 0x7f3130a7ee29 process::ProcessManager::resume()
Attachments
Issue Links
- duplicates
-
MESOS-9267 Mesos agent crashes when CNI network is not configured but used.
- Resolved