Mirantis OpenStack

Request to backport a patch from upstream (DVR Pings to floating IPs replied with fixed-ips if VMs are on the same network)

Bug #1630242 reported by Maxim V. Yefimov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
High
Alexey Stupnikov
Mirantis OpenStack 7.0-updates
8.0.x
Won't Fix
High
Alexey Stupnikov
Mirantis OpenStack 8.0-updates

Bug Description

The customer (MOS 7.0 cloud) reported that they had experienced a issue described here: https://bugs.launchpad.net/neutron/+bug/1462154

Please backport the suggested patch: https://review.openstack.org/#/c/378374/

Maxim V. Yefimov (mefimov)
tags: added: ct1
Vitaly Sedelnik (vsedelnik)
Changed in mos:
importance: Undecided → High
assignee: nobody → MOS Maintenance (mos-maintenance)
Rodion Tikunov (rtikunov)
Changed in mos:
assignee: MOS Maintenance (mos-maintenance) → Rodion Tikunov (rtikunov)
Vitaly Sedelnik (vsedelnik)
Changed in mos:
status: New → Confirmed
Revision history for this message
Rodion Tikunov (rtikunov) wrote :

Proposed fix: https://review.fuel-infra.org/#/c/27395/

Changed in mos:
status: Confirmed → In Progress
Rodion Tikunov (rtikunov)
Changed in mos:
status: In Progress → Fix Committed
Revision history for this message
Rodion Tikunov (rtikunov) wrote :

Proposed for 8.0 fix: https://review.fuel-infra.org/#/c/27511/

Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Verified on MOS 7.0 + MU6 updates.

Steps to verify are taken from description of bug https://bugs.launchpad.net/neutron/+bug/1462154.

Actual results:
Ping replies came from VM2's floating ip address.

Changed in mos:
status: Fix Committed → Fix Released
TatyanaGladysheva (tgladysheva)
tags: added: on-automation
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Test case is automated: https://review.gerrithub.io/#/c/298661

tags: added: covered-automated-test
removed: on-automation
Revision history for this message
Rodion Tikunov (rtikunov) wrote :

Fix for 7.0 has been reverted due to bug https://bugs.launchpad.net/mos/+bug/1641762
Confirm it again

Changed in mos:
assignee: Rodion Tikunov (rtikunov) → MOS Neutron (mos-neutron)
status: Fix Released → Confirmed
Denis Meltsaykin (dmeltsaykin)
Changed in mos:
milestone: 7.0-mu-6 → 7.0-mu-7
Denis Meltsaykin (dmeltsaykin)
Changed in mos:
milestone: 7.0-mu-7 → 7.0-updates
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Moving from 8.0-mu-4 since this patch introduces another serious issue and the initial report was for 7.0.

Alexey Stupnikov (astupnikov)
Changed in mos:
assignee: MOS Neutron (mos-neutron) → Alexey Stupnikov (astupnikov)
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

Won't fix for 7.0-updates as we no longer support it.

Changed in mos:
status: Confirmed → Won't Fix
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

I have reviewed 8.0 fix and it looks like a highly customized code to me. As a result, we can't say that those code was tested somewhere and we will merge it at our own risk. Since MOS8 is not actively supported at the moment, we can't merge such fix. Closing as Won't fix for 8.0-updates.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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