Hi Nobin, +public controller-dev, hope that's:
On Wed, Jun 6, 2018 at 11:46 AM, Josh Hershberg <jhers...@redhat.com> wrote: > I've never seen that. There's an option to install features where you > specify not to reinitialize dependencies or something like that. Try with > that. Adding vorburger. > the option Josh is thinking of is "--no-auto-refresh" ... you can try to do it like this to see if this makes any difference and helps - if it does, it would be great to hear back from you. You would use it like this: feature:install odl-mdsal-trace feature:install --no-auto-refresh odl-netvirt-openstack odl-restconf-all I thought this was no longer neccessary because stuff related to that got fixed... but perhaps that never made it into stable/oxygen. Ideally if you could try it against master, first, that could help to clarify what's going on here. See also these earlier (now resolved) issue related to this: * https://jira.opendaylight.org/browse/NEUTRON-153 * https://jira.opendaylight.org/browse/NETCONF-516 * https://jira.opendaylight.org/browse/CONTROLLER-1764 On Wed, Jun 6, 2018, 12:26 Nobin Mathew <nobin.mat...@ericsson.com> wrote: > >> Hi Josh, >> >> >> >> After loading mdsal-trace, other bundles are not getting loaded. >> >> >> >> This is on yesterday’s stable oxygen. >> >> >> >> Feature install order is below: >> >> >> >> feature:install odl-mdsal-trace >> >> feature:install odl-netvirt-openstack odl-restconf-all >> >> >> >> If I don’t load mdsal-trace, then everything works fine. >> >> >> >> First exception is attached >> > attachments don't survive replies, forwards and mailing lists.. ;-) If the tips above do not help, then could you copy/paste the log to some place such as https://paste.fedoraproject.org and reply with the link to it here? HTH, M. -- Michael Vorburger, Red Hat vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch -Nobin >> >> >> >> *From:* Nobin Mathew >> *Sent:* Wednesday, June 06, 2018 12:06 PM >> *To:* 'Josh Hershberg' <jhers...@redhat.com> >> *Subject:* using mdsaltrace >> >> >> >> Hi Josh, >> >> >> >> I am planning to trace exactly when ovsdb node addition to topology oper >> datastore happens when a new switch connects. >> >> >> >> 1) I will add these lines in etc/opendaylight/datastore/ini >> tial/config/mdsaltrace_config.xml >> >> >> >> <*registration-watches*> /NetworkTopology/Topology</ >> *registration-watches*> >> >> <*write-watches*> /NetworkTopology/Topology</*write-watches*> >> >> >> >> >> >> >> >> Now the second part >> >> >> >> 2) I have one distribution repo and one ovsdb repo >> >> >> >> >> >> a) What I was planning to do was change dependency in ovsdb pom xmls and >> build, then replace the jar in distribution with these. >> >> And finally I will run the distribution. >> >> >> >> >> >> For this I changed >> >> >> >> >> https://github.com/opendaylight/ovsdb/blob/master/southbound/southbound-karaf/pom.xml >> >> >> https://github.com/opendaylight/ovsdb/blob/master/library/karaf/pom.xml >> >> >> https://github.com/opendaylight/ovsdb/blob/master/hwvtepsouthbound/hwvtepsouthbound-karaf/pom.xml >> >> >> >> In above three files I added mdsaltrace dependency. >> >> >> >> b) Built ovsdb repo >> >> c) Now which jar from these repo I need copy to distribution build? >> >> >> >> Thanks, >> >> -Nobin >> >>
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
