You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2019/01/10 20:44:00 UTC
[jira] [Commented] (MESOS-9518) CNI_NETNS should not be set for
orphan containers that do not have network namespace
[ https://issues.apache.org/jira/browse/MESOS-9518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739761#comment-16739761 ]
Jie Yu commented on MESOS-9518:
-------------------------------
Fix: https://reviews.apache.org/r/69706/
Adding tests now.
> CNI_NETNS should not be set for orphan containers that do not have network namespace
> ------------------------------------------------------------------------------------
>
> Key: MESOS-9518
> URL: https://issues.apache.org/jira/browse/MESOS-9518
> Project: Mesos
> Issue Type: Bug
> Components: cni
> Affects Versions: 1.4.2, 1.5.1, 1.6.1, 1.7.0
> Reporter: Jie Yu
> Assignee: Jie Yu
> Priority: Major
>
> We introduced a new agent flag in MESOS-9492 so that CNI configs can be persisted across reboot. This is for some CNI plugins to be able to cleanup IP allocated to the containers after a sudden reboot of the host (not all CNI plugins need this).
> It's important to unset `CNI_NETNS` environment variable after reboot when invoking CNI plugin "DEL" command so that it conforms to the spec:
> {noformat}
> When CNI_NETNS and/or prevResult are not provided, the plugin should clean up as many resources as possible (e.g. releasing IPAM allocations) and return a successful response.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)