Introspect request for UVE cache shows incorrect sequence number for NodeStatusUVE in contrail-topology

Bug #1533619 reported by Sundaresan Rajangam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
High
Sundaresan Rajangam

Bug Description

In contrail-topology, introspect request for UVE cache shows incorrect sequence number [seq_num: 0] for NodeStatusUVE.

This issue is due to importing NodeStatusUVE from different packages in init_generator() [contrail_topology.sandesh] and ConnectionState.init [opserver.sandesh].

Tags: analytics
description: updated
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/16265
Submitter: Sundaresan Rajangam (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/16265
Committed: http://github.org/Juniper/contrail-controller/commit/b0404dbda74827cd903d3ef42c2e9ecb4de5adc0
Submitter: Zuul
Branch: master

commit b0404dbda74827cd903d3ef42c2e9ecb4de5adc0
Author: Sundaresan Rajangam <email address hidden>
Date: Wed Jan 13 04:03:49 2016 -0800

Fix incorrect sequence number for NodeStatus UVE in contrail-topology

Issue:
In contrail-topology, introspect request for UVE cache shows incorrect
sequence number [seq_num: 0] for NodeStatusUVE. This issue is due to
importing NodeStatusUVE from different packages in init_generator()
[contrail_topology.sandesh] and ConnectionState.init [opserver.sandesh].

Fix:
Import NodeStatusUVE from contrail_topology.sandesh

Change-Id: I320645276a688650b25694cc5ac96cb4fbaf80fe
Closes-Bug: #1533619

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.