v2 driver: too many skipping row on same resource in short period

Bug #1646681 reported by Isaku Yamahata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-odl
Fix Released
High
rajiv

Bug Description

There are too many "skipping for now" message on same resource in short time.

With tempest log, there are the following log.
https://review.openstack.org/#/c/382597
http://logs.openstack.org/97/382597/7/check/gate-tempest-dsvm-networking-odl-carbon-snapshot/5d5f8c1/logs/screen-q-svc.txt.gz?level=DEBUG#_2016-12-01_21_38_13_726

The following message are repeated in short term.
This indicates v2 driver doesn't behave expectedly.

2016-12-01 21:38:13.726 23872 INFO networking_odl.journal.journal [-] delete network b0e09ec2-b3d8-4a99-a086-d7b567913bec is not a valid operation yet, skipping for now
2016-12-01 21:38:13.729 23872 DEBUG networking_odl.journal.journal [-] Thread walking database _sync_pending_rows /opt/stack/new/networking-odl/networking_odl/journal/journal.py:165
2016-12-01 21:38:13.736 23872 INFO networking_odl.journal.journal [-] delete network b0e09ec2-b3d8-4a99-a086-d7b567913bec is not a valid operation yet, skipping for now
2016-12-01 21:38:13.739 23872 DEBUG networking_odl.journal.journal [-] Thread walking database _sync_pending_rows /opt/stack/new/networking-odl/networking_odl/journal/journal.py:165
2016-12-01 21:38:13.746 23872 INFO networking_odl.journal.journal [-] delete network b0e09ec2-b3d8-4a99-a086-d7b567913bec is not a valid operation yet, skipping for now
2016-12-01 21:38:13.749 23872 DEBUG networking_odl.journal.journal [-] Thread walking database _sync_pending_rows /opt/stack/new/networking-odl/networking_odl/journal/journal.py:165
2016-12-01 21:38:13.758 23872 INFO networking_odl.journal.journal [-] delete network b0e09ec2-b3d8-4a99-a086-d7b567913bec is not a valid operation yet, skipping for now
2016-12-01 21:38:13.760 23872 DEBUG networking_odl.journal.journal [-] Thread walking database _sync_pending_rows /opt/stack/new/networking-odl/networking_odl/journal/journal.py:165
2016-12-01 21:38:13.768 23872 INFO networking_odl.journal.journal [-] delete network b0e09ec2-b3d8-4a99-a086-d7b567913bec is not a valid operation yet, skipping for now
2016-12-01 21:38:13.772 23872 DEBUG networking_odl.journal.journal [-] Thread walking database _sync_pending_rows /opt/stack/new/networking-odl/networking_odl/journal/journal.py:165

Changed in networking-odl:
importance: Undecided → High
rajiv (rajiv-kumar)
Changed in networking-odl:
assignee: nobody → rajiv (rajiv-kumar)
Revision history for this message
Isaku Yamahata (yamahata) wrote :

Given this probably is fixed by Pike.
So closing it for now.
If you still observe the issue with pike or later, please reopen it.

Changed in networking-odl:
status: New → Fix Released
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.