[NETVIRT-1533] IllegalArgumentException: Node elan-interface is missing mandatory descendant /elan-instance-name Created: 05/Dec/18  Updated: 25/Nov/19  Resolved: 25/Nov/19

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: None
Fix Version/s: Neon

Type: Bug Priority: Medium
Reporter: Michael Vorburger Assignee: Faseela K
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File karaf-NETVIRT-1533.log     File karaf.log.NETVIRT-1533.gz     File karaf.log.gz     Text File pod-coe.txt    
Issue Links:
Blocks
blocks COE-46 Production Quality CoE Open
Duplicate
is duplicated by NETVIRT-1532 NFE in CoeUtils.buildElanInstance() Resolved

 Description   

While debugging my COE-36 today, k.faseela noticed this:

Caused by: java.lang.IllegalArgumentException: Node (urn:opendaylight:netvirt:elan?revision=2015-06-02)elan-interface[{(urn:opendaylight:netvirt:e
lan?revision=2015-06-02)name=00000000-0000-0000-0000-000000000001:busybox-1.1}] is missing mandatory descendant /(urn:opendaylight:netvirt:elan?re
vision=2015-06-02)elan-instance-name

FYI shague fkautz prem.sankar.g@ericsson.com

Fully details in attached karaf.log

 Comments   
Comment by Faseela K [ 10/Dec/18 ]

vorburger : If you have not already started taking stable/fluorine, I think this patch on watcher should solve your current problem in neon. Can you try building the watcher with this patch, and see if things work?

Comment by Michael Vorburger [ 10/Dec/18 ]

Sure, I'll give it a go, hopefully on Wednesday.

Comment by Michael Vorburger [ 13/Dec/18 ]

k.faseela just FTR, in the last test today (which you helped with on IRC, thanks again!) I'm actually still seeing this IllegalArgumentException: Node elan-interface[\{name=00000000-0000-0000-0000-000000000001:busybox-1.1}] is missing mandatory descendant /elan-instance-name" problem in the attached karaf-NETVIRT-1533.log, BUT as you saw the pod ping worked now. Indeed the 3 changes linked to this Jira don't seem to fix anything which would add e.g. setElanInstanceName() so suspect that those changes actually fixed another (more important) issue. Do you want to check if your CSIT contain this error as well, and re-open this issue?

Comment by Faseela K [ 14/Dec/18 ]

vorburger : Will you be able to give me the logs with TRACE enabled for 

org.opendaylight.netvirt.coe next time?

Comment by Faseela K [ 14/Dec/18 ]

Also, please give me the pod:coe output once the logs are seen

Comment by Michael Vorburger [ 17/Dec/18 ]

opendaylight-user@root>log:set TRACE org.opendaylight.netvirt.coe

Comment by Michael Vorburger [ 17/Dec/18 ]

Attached as requested new karaf.log.gz with additional TRACE, and output of "http -a admin:admin GET http://localhost:8181/restconf/config/pod:coe" as pod-coe.txt. This is after having "reset" things as instructed on IRC the other day, now scripted in my clean-full-COE.sh.

Comment by Michael Vorburger [ 17/Dec/18 ]

k.faseela I just noticed your https://git.opendaylight.org/gerrit/#/c/78789 for this; if others are OK with it, just get it in!

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