You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2018/08/01 22:24:00 UTC
[jira] [Assigned] (MESOS-9125) Port mapper CNI plugin might fail
with "Resource temporarily unavailable"
[ https://issues.apache.org/jira/browse/MESOS-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Mann reassigned MESOS-9125:
--------------------------------
Assignee: Greg Mann
> Port mapper CNI plugin might fail with "Resource temporarily unavailable"
> -------------------------------------------------------------------------
>
> Key: MESOS-9125
> URL: https://issues.apache.org/jira/browse/MESOS-9125
> Project: Mesos
> Issue Type: Bug
> Components: network
> Affects Versions: 1.4.1, 1.5.1, 1.6.1
> Reporter: Jie Yu
> Assignee: Greg Mann
> Priority: Major
>
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/mesos/isolators/network/cni/plugins/port_mapper/port_mapper.cpp#L345
> Looks like we're missing a `-w` for the iptable command. This will lead to issues like
> {noformat}
> The CNI plugin '/opt/mesosphere/active/mesos/libexec/mesos/mesos-cni-port-mapper' failed to attach container a710dc89-7b22-493b-b8bb-fb80a99d5321 to CNI network 'mesos-bridge': stdout='{"cniVersion":"0.3.0","code":103,"msg":"Failed to add DNAT rule with tag: Resource temporarily unavailable"}
> {noformat}
> This becomes more likely if there are many concurrent launches of Mesos contianers that uses port mapper on the box.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)