[GENIUS-200] Make Genius CSIT fail in case any exceptions are seen in karaf logs Created: 31/Jul/18  Updated: 02/Aug/18

Status: Open
Project: genius
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Medium
Reporter: Faseela K Assignee: Vishal Thapar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by GENIUS-194 IdManagerException: Ids exhausted for... Open
is blocked by GENIUS-196 Optimistic lock failed for path /(urn... Open
is blocked by GENIUS-197 Deletion of default-transport-zone is... Resolved
is blocked by SRVUTILS-3 Failed to prepare transaction member-... To Do
is blocked by GENIUS-133 Genius SRM CSIT failure – OVS port de... Verified
is blocked by GENIUS-195 Transport Zone default-transport-zone... Verified

 Description   

As we recently analyzed, we have seen a lot of exceptions in karaf logs, once genius CSIT runs. vorburger has raised separate JIRAs for each of the exceptions seen. In future it will be good if CSIT marks failure if any of the patches introduce new exceptions. shague and jluhrsen have already done this for netvirt CSIT, would like to follow the same procedure for genius CSIT

 Comments   
Comment by Michael Vorburger [ 02/Aug/18 ]

>  has raised separate JIRAs for each of the exceptions seen

I've just linked them all; background is https://lists.opendaylight.org/pipermail/genius-dev/2018-July/003212.html

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