yahoo-eng-team team mailing list archive

[Kevin Benton <1288441@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When the tests for FWaaS create a firewall and then delete it, the
firewall object is still in the database in a PENDING_DELETE state
waiting for the agent to remove it. Parent objects then can't be deleted
because the firewall object is dependent on them.

Currently, all of the tests just leave the parent objects by using
no_delete[1], which leaves things in the database and could lead to some
kinds of conflicts later.

1.
https://github.com/openstack/neutron/blob/ac8c0c645de001a0d074cdfd9448f9680a5d5e34/neutron/tests/unit/db/firewall/test_db_firewall.py#L732

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1288441

Title:
  FWaaS tests don't delete firewalls

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When the tests for FWaaS create a firewall and then delete it, the
  firewall object is still in the database in a PENDING_DELETE state
  waiting for the agent to remove it. Parent objects then can't be
  deleted because the firewall object is dependent on them.

  Currently, all of the tests just leave the parent objects by using
  no_delete[1], which leaves things in the database and could lead to
  some kinds of conflicts later.

  1.
  https://github.com/openstack/neutron/blob/ac8c0c645de001a0d074cdfd9448f9680a5d5e34/neutron/tests/unit/db/firewall/test_db_firewall.py#L732

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1288441/+subscriptions