[ https://issues.apache.org/jira/browse/MESOS-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Osborne updated MESOS-5453: ------------------------------- Description: 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) was: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 > 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 > > 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)