yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77818
[Bug 1822968] [NEW] "lbaas delete l7 rule & policy" could leave dirty data
Public bug reported:
"lbaas delete l7 rule & policy" could leave dirty data
In lbaas plugin side, the logic for deleting l7 rule and l7 policy is as follows:
If the l7 rule(or policy) attached to a load balancer, plugin only calls drivers to delete data (without any database operations); otherwise plugin deletes the data in database.
The codes are as follows:
if l7policy_db.attached_to_loadbalancer():
driver = self._get_driver_for_loadbalancer(
context, l7policy_db.listener.loadbalancer_id)
self._call_driver_operation(context, driver.l7policy.delete,
l7policy_db)
else:
self.db.delete_l7policy(context, id)
As a result:
When try to delete the l7 rule(or policy) attached to a load balancer,
dirty data will be left in the database.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: lbaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1822968
Title:
"lbaas delete l7 rule & policy" could leave dirty data
Status in neutron:
New
Bug description:
"lbaas delete l7 rule & policy" could leave dirty data
In lbaas plugin side, the logic for deleting l7 rule and l7 policy is as follows:
If the l7 rule(or policy) attached to a load balancer, plugin only calls drivers to delete data (without any database operations); otherwise plugin deletes the data in database.
The codes are as follows:
if l7policy_db.attached_to_loadbalancer():
driver = self._get_driver_for_loadbalancer(
context, l7policy_db.listener.loadbalancer_id)
self._call_driver_operation(context, driver.l7policy.delete,
l7policy_db)
else:
self.db.delete_l7policy(context, id)
As a result:
When try to delete the l7 rule(or policy) attached to a load balancer,
dirty data will be left in the database.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1822968/+subscriptions
Follow ups