Port-chain delete port-pair details also

Bug #1673078 reported by vks1
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-sfc
Incomplete
Undecided
vks1

Bug Description

Currently port-chain delete leads to delete of port-pair details also from db. If tried to recreate port-chain with same ppg and classifier, create fails.

Steps to reproduce:

1. Create port-chain (pc1) with classifier class1 and port-pair-group ppg1.
2. Delete pc1
3. Redo (1).

vks1 (vikash-kumar)
Changed in networking-sfc:
assignee: nobody → vks1 (vikash-kumar)
Revision history for this message
Igor D.C. (igordcard) wrote :

Hi Vikash, I can't reproduce this issue, can you more details about the port chain being created?
Non-portpair portpairdetails should be removed from the db when the chain is deleted.

Revision history for this message
vks1 (vikash-kumar) wrote :

Hi Igor,

I created a port chain (pc1) and then deleted the same pc1 (only). I tried to recreate the same pc1 with the same port-pair group and flow classifier and it failed. I checked the log. Please find it here:

http://paste.openstack.org/show/602904/

And after I debugged:
https://github.com/openstack/networking-sfc/blob/master/networking_sfc/services/sfc/drivers/ovs/driver.py#L344

pd1 was None as the DB entry was getting deleted.

Revision history for this message
Igor D.C. (igordcard) wrote :

Hi Vikash,

I still can't reproduce the issue, see http://paste.openstack.org/show/603388. Tested with latest master (17c537b35d41a3e1fd80da790ae668e52cea6b88), I expect there is something else triggering this issue for you, can you provide more context please? Also, can you test this commit without any other changes?

Louis Fourie (lfourie)
Changed in networking-sfc:
status: New → Incomplete
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on networking-sfc (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/445979
Reason: This review is > 3 months without comment and currently blocked by a core reviewer with a -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -1 on this review to ensure you address their concerns.

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.