Bug 1472182 - Entries in the journal are not processed occasionally
Summary: Entries in the journal are not processed occasionally
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-odl
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: Upstream M3
: 12.0 (Pike)
Assignee: Mike Kolesnik
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-18 08:41 UTC by Itzik Brown
Modified: 2018-10-18 07:25 UTC (History)
2 users (show)

Fixed In Version: python-networking-odl-11.0.0-0.20170719125820.14ee893.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
N/A
Last Closed: 2017-12-13 21:42:20 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1703295 0 None None None 2017-07-18 08:41:59 UTC
OpenStack gerrit 482042 0 None None None 2017-07-23 12:32:42 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Itzik Brown 2017-07-18 08:41:59 UTC 
Description of problem:
Entries in the journal (e.g. floating IP creation etc.) are stuck in 'pending' state.
This cause

Version-Release number of selected component (if applicable):
python-networking-odl-11.0.0-0.20170710194836.ba60ac7.el7ost.noarch

How reproducible:
Occasionally 

Steps to Reproduce:
1. Access the ovs_neutron database
2. Run the query: object_type,object_uuid,state,operation from opendaylightjournal;
3. Watch for entries that are in 'pending' state.

Actual results:


Expected results:


Additional info:
Comment 2 Itzik Brown 2017-08-03 10:43:54 UTC 
Didn't see any entries in pending after launching couple of instances.
Verified the the code exist.

Checked with:
python-networking-odl-11.0.0-0.20170721155128.a047729.el7ost.noarch
Comment 5 errata-xmlrpc 2017-12-13 21:42:20 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462
Note You need to log in before you can comment on or make changes to this bug.