yahoo-eng-team team mailing list archive

[Salvatore Orlando <1290549@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Logs are showing plenty of tracebacks like the following:
http://logs.openstack.org/96/66796/15/check/check-tempest-dsvm-neutron-
full/d940e56/logs/screen-q-svc.txt.gz?level=DEBUG#_2014-03-06_10_14_46_352

An operation (either update_floatingip_status or get_floating_ips) in
update_floatingip_statuses (l3_rpc_base.py) triggers this traceback.
Apparently this happens because if a floatingIP is removed, the
transaction is aborted because of the exception.

Optimizing as suggested here:
https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L680
might solve the issue.

** Affects: neutron
     Importance: Medium
     Assignee: Salvatore Orlando (salvatore-orlando)
         Status: New


** Tags: l3

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

Title:
  update floatingip status tracebacks

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Logs are showing plenty of tracebacks like the following:
  http://logs.openstack.org/96/66796/15/check/check-tempest-dsvm-
  neutron-
  full/d940e56/logs/screen-q-svc.txt.gz?level=DEBUG#_2014-03-06_10_14_46_352

  An operation (either update_floatingip_status or get_floating_ips) in
  update_floatingip_statuses (l3_rpc_base.py) triggers this traceback.
  Apparently this happens because if a floatingIP is removed, the
  transaction is aborted because of the exception.

  Optimizing as suggested here:
  https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L680
  might solve the issue.

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