Instances on the same compute node unable to connect to each other's ports

Bug #1511668 reported by Eugene Nikanorov
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
High
Eugene Nikanorov
6.1.x
Fix Released
High
Denis Puchkin
7.0.x
Invalid
High
Denis Puchkin
8.0.x
Invalid
High
Eugene Nikanorov

Bug Description

Using conntrack zone per network may prevent VMs residing on the same compute node to properly shutdown the connection.
When one VM initiate termination by issuing TCP reset, conntract will automatically treat the connection as closed, so other VM on the same compute will not get incoming TCP reset, because conntrack will think that it's a packet of non-existent (already) connection.

Corresponding upstream bug: https://bugs.launchpad.net/neutron/+bug/1478925

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Need to backport https://review.openstack.org/207464
This should be included in 7.0 MU-2

Changed in mos:
milestone: none → 7.0-updates
no longer affects: mos/8.0.x
Changed in mos:
milestone: 7.0-updates → 7.0-mu-2
tags: added: support
Changed in mos:
milestone: 7.0-mu-2 → 7.0-updates
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

According to https://bugs.launchpad.net/neutron/+bug/1478925 this has been fixed in Liberty - closing as Invalid for 8.0

tags: added: area-neutron
no longer affects: mos/9.0.x
Revision history for this message
Denis Puchkin (dpuchkin) wrote :

invalid for 6.1 and 7.0

the patch https://review.fuel-infra.org/#/q/Ie6ce5f3fa688f1bf25b77db5955211922d9fe85b,n,z fix this issue

This patch was published in Mirantis OpenStack 6.1-mu-5 and Mirantis OpenStack 7.0-mu-2

Changed in mos:
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.