database consistency problem for deleting router gateway port

Bug #1566678 reported by RaoFei
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Kevin Benton

Bug Description

* Summary
When deleting l3 router gateway port, if the gateway port deleting fail, then this gateway port cannot be delete any more.

* Pre-conditions
A vrouter is created with an external gateway port.

* Step-by-step
1. loop add and delete gateway port.
2. loop kill the neutron-server and restart

* Expect output
The gateway port can be deleted or added successfully.

* Actual output
The gateway port is stale and cannot be deleted.

RaoFei (milo-frao)
tags: added: db
Changed in neutron:
assignee: nobody → Anseela M M (anseela-m00)
Gary Kotton (garyk)
tags: added: l3-ipam-dhcp
Revision history for this message
Anseela M M (anseela-m00) wrote :

Hi
Currently I am working on this issue.
For that I have done the below steps:
1) Created a network and added subnet to that
2) Created a router and linked the router to the subnet
3) then created a network port using the command
 neutron port-create mypublic --fixed-ip ip_address=172.56.26.1
4) then killed the neutron-server process and restarted the same
5) tried to delete the neutron port

I am able to delete created neutron port.

Please let me know the steps which i have done, is correct or not
let me know how to loop the add and delete gateway port.

Thanks
Anseela

Revision history for this message
Kevin Benton (kevinbenton) wrote :

This was already fixed in Mitaka here: https://github.com/openstack/neutron/commit/3b41808b8624f5442d65ba638d1a2c1bdc22be00

I suspect this bug may have been discovered on liberty? Marking as duplicate unless this has been observed in Mitaka or master.

Revision history for this message
Kevin Benton (kevinbenton) wrote :

Well actually just marking as fix released because the bug for that patch had to do with HA interfaces, but it's the same underlying issue.

Changed in neutron:
status: New → Fix Released
assignee: Anseela M M (anseela-m00) → Kevin Benton (kevinbenton)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/liberty)

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/308142

Revision history for this message
Kevin Benton (kevinbenton) wrote :
Changed in neutron:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/liberty)

Reviewed: https://review.openstack.org/308142
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6b33c51a32e075c57630160b5b0544ad29f1a3bb
Submitter: Jenkins
Branch: stable/liberty

commit 6b33c51a32e075c57630160b5b0544ad29f1a3bb
Author: Kevin Benton <email address hidden>
Date: Mon Feb 1 01:17:22 2016 -0800

    Only prevent l3 port deletion if router exists

    This patch modifies the prevent_l3_port_deletion method to
    actually look up the router_id in the device_owner field to
    confirm that the router exists before claiming the port is
    in use. This will allow users to delete ports that may have
    been orphaned due to race conditions in the cleanup of router
    interfaces.

    Conflicts:
     neutron/tests/unit/db/test_l3_db.py

    Closes-Bug: #1566678
    Partial-Bug: #1540271
    Change-Id: Ieffe632f3f3098baf202d3795ab5182982e234bd
    (cherry picked from commit 3b41808b8624f5442d65ba638d1a2c1bdc22be00)

tags: added: in-stable-liberty
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/neutron 7.1.0

This issue was fixed in the openstack/neutron 7.1.0 release.

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

Other bug subscribers

Remote bug watches

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