You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Dan Osborne (JIRA)" <ji...@apache.org> on 2016/05/27 17:20:12 UTC

[jira] [Commented] (MESOS-5453) CNI should not store subnet of address in NetworkInfo

    [ https://issues.apache.org/jira/browse/MESOS-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304377#comment-15304377 ] 

Dan Osborne commented on MESOS-5453:
------------------------------------

https://reviews.apache.org/r/47971/

> CNI should not store subnet of address in NetworkInfo
> -----------------------------------------------------
>
>                 Key: MESOS-5453
>                 URL: https://issues.apache.org/jira/browse/MESOS-5453
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Dan Osborne
>            Assignee: Dan Osborne
>              Labels: mesosphere
>             Fix For: 0.29.0
>
>
> When the CNI isolator executes the CNI plugin, that CNI plugin will return an IP Address and Subnet (192.168.0.1/32). Mesos should strip the subnet before storing the address in the Task.NetworkInfo.IPAddress.
> Reason being - most current mesos components are not expecting a subnet in the Task's NetworkInfo.IPAddress, and instead expect just the IP address. This can cause errors in those components, such as Mesos-DNS failing to return a NetworkInfo address (and instead defaulting to the next configured IPSource), and Marathon generating invalid links to tasks (as it includes /32 in the link)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)