https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLPARENT-97 odlparent <p>It seems like there are a few possible ways forward: (1) use the karaf 3 resolver in karaf 4, (2) fix all bundles/features to be reloadable, (3) we could move to using dependency=true, which won't reload them, but it doesn't load them for you, it's possible that adding prerequisite=true as well would fix it, but that seems to expose bugs in Karaf, (4) figure out if we can effectively enable --no-auto-refresh</p> <p>Operating System: All<br/> Platform: All</p> ODLPARENT-97

Karaf 4 Dependency Resolution

Bug Resolved Cannot Reproduce Unassigned A H Wed, 7 Jun 2017 15:35:31 +0000 Wed, 24 Jan 2018 14:26:40 +0000 Tue, 25 Jul 2017 16:26:55 +0000 2.0.5 General 0 4 <p>As far as I understood in yesterday's Kernel call, skitt is investigating this..</p> <p>Upstream’s view on this is that we need to sort out our refresh issues before we start investigating any remaining dependency issues. The default dependency handling should be OK for us apparently.</p> <p>I’m guessing we might still need prerequisite="true" for some dependencies, e.g. the data broker...</p> <p>Just so that people can find it. This thread with Stephen Kitt upstream in Karaf:<br/> <a href="http://karaf.922171.n3.nabble.com/Understanding-features-and-dependencies-td4050692.html#a4050698" class="external-link" target="_blank" rel="nofollow noopener">http://karaf.922171.n3.nabble.com/Understanding-features-and-dependencies-td4050692.html#a4050698</a></p> <p>Has Karaf saying that the general issue is our refreshes not dependency resolution being broken. Also, feature:install should not be refreshing bundles as a matter of course. Instead if we're seeing refreshes, that's probably a bug.</p> <p>This meeting has some notes too around section 2:<br/> <a href="https://meetings.opendaylight.org/opendaylight-meeting/2017/nitrogen_release_sync/opendaylight-meeting-nitrogen_release_sync.2017-06-19-15.02.html" class="external-link" target="_blank" rel="nofollow noopener">https://meetings.opendaylight.org/opendaylight-meeting/2017/nitrogen_release_sync/opendaylight-meeting-nitrogen_release_sync.2017-06-19-15.02.html</a></p> <ul> <li>colindixon asks if there are patterns to what breaks in karaf 4 that we can look for (colindixon, 15:12:33)</li> <li>skitt says that there are some things which are bugs that happened to work in karaf 3, but don't work anymore (colindixon, 15:13:00)</li> <li><a href="https://lists.opendaylight.org/pipermail/netvirt-dev/2017-June/004788.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/netvirt-dev/2017-June/004788.html</a> &lt;== this is, AFAIK, the latest on where netvirt is at (Karaf 4 is NOK; many CSIT still failing for them) (vorburger, 15:13:47)</li> <li>other times are when karaf 4 tracks package dependcies much more closely and refreshses things when they change those, in netconf, this seems to have happened when there are package exports that aren't really needed espcially when there are cycles (colindixon, 15:14:57)</li> <li>also optional dependecies now trigger refreshes if they become available (colindixon, 15:15:32)</li> </ul> <p>If you do feature:install -v it should note if it refreshes any bundles and if so, why. That should help figure things out.</p> Blocks NETVIRT-733 ODLPARENT-23 NETCONF-213 Development External issue ID 8622 External issue URL ODL SR Target Milestone Rank 0|i023af: