[OVSDB-335] OVSDB Distribution Test Failures Beryllium SR2 Created: 27/Apr/16  Updated: 19/Oct/17  Resolved: 09/May/16

Status: Resolved
Project: ovsdb
Component/s: Other
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: A H Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5809

 Description   

Bug to track the distribution test failures in OVSDB for Beryllium SR2 release. If more specific bugs are found after further investigation, then we can close this bug and point to the new individual BUG IDs.

https://jenkins.opendaylight.org/releng/job/ovsdb-csit-1node-netvirt-all-beryllium/946/
https://jenkins.opendaylight.org/releng/job/ovsdb-csit-1node-southbound-only-beryllium/1071/
https://jenkins.opendaylight.org/releng/job/ovsdb-csit-1node-southbound-all-beryllium/938/

Current email thread to discuss the investigation:
https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-April/002943.html

 Comments   
Comment by Jamo Luhrsen [ 27/Apr/16 ]

two issues identified so far.

1) same thread from first comment:
https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-April/002959.html

2) without longer wait time when loading features, br-int is not created. thread to track that:
https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-April/002958.html

Comment by A H [ 29/Apr/16 ]

A patch for this bug was submitted:

https://git.opendaylight.org/gerrit/#/c/38212/

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:

Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note and fix in future Beryllium SR3?
Testing: Could you also elaborate on the testing or this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?
Impact: Does this fix impact any dependent projects?

Comment by Anil Vishnoi [ 02/May/16 ]

(In reply to A H from comment #2)
> A patch for this bug was submitted:
>
> https://git.opendaylight.org/gerrit/#/c/38212/
>
> To better assess the impact of this bug and fix, could someone from your
> team please help us identify the following:
>
> Severity: Could you elaborate on the severity of this bug? Is this a
> BLOCKER such that we cannot release Beryllium without it?
Yes, this breaks the existing functionality where plugin can't populate the operational data store with the termination points available on the bridge.

Is there a
> workaround such that we can write a release note and fix in future Beryllium
> SR3?
I believe no, because current behavioural change of yangtools equal caused this error, so this need to be fixed in code to make it work.
> Testing: Could you also elaborate on the testing or this patch? How
> extensively has this patch been tested? Is it covered by any unit tests or
> system tests?
Yes, Existing system tests help detecting the issue, once all failing test passes, that verify that patch fixes the issue.
> Impact: Does this fix impact any dependent projects?
No

Comment by A H [ 09/May/16 ]

Have we verified if the bug has been fixed in the latest build for Beryllium SR2?

https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Beryllium_SR2_Download

Comment by Jamo Luhrsen [ 09/May/16 ]

(In reply to A H from comment #4)
> Have we verified if the bug has been fixed in the latest build for Beryllium
> SR2?
>
> https://wiki.opendaylight.org/view/Simultaneous_Release:
> Beryllium_Release_Plan#Beryllium_SR2_Download

yes, it has been verified to still be fixed in latest Be SR2 distribution.

Generated at Wed Feb 07 20:36:07 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.