Operating System: All
Platform: All

Attachment karaf.log has been added with description: karaf.log

Attachment bundle-diag.log has been added with description: bundle:diag

Did you try installing 'odl-l2switch-switch-ui'
The above feature should install both switch & dlux-node features and it works.

Feature dependency graph for easy reference is here -> https://wiki.opendaylight.org/images/5/56/Feature_dependency_graph.PNG

> Did you try installing 'odl-l2switch-switch-ui'

I did and this is working fine, yes. But it doesn't prevent the reported BUG to occur.

The issue seems to be the Guava bundle refreshing thus refreshing the whole core of OpenDaylight.
Do Guava bundle don't need to be tied to the feature, as it is only needed as a dependency.

https://git.opendaylight.org/gerrit/#/q/topic:bug/6956

(In reply to Alexis de Talhouët from comment #4)
> > Did you try installing 'odl-l2switch-switch-ui'
>
> I did and this is working fine, yes. But it doesn't prevent the reported BUG
> to occur.

Agreed. I was making sure that end user knows the above feature usability.

Boron --> https://git.opendaylight.org/gerrit/#/q/topic:bug/6956-stable/boron
Carbon --> https://git.opendaylight.org/gerrit/#/q/topic:bug/6956

Reopening blocker bug for Boron-SR1

A patch was submitted to fix this bug in Boron SR1: https://git.opendaylight.org/gerrit/#/c/47225/

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Regression: Is this bug a regression of functionality/performance/feature compared to Boron (Build RC3.5)?
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron-SR1 without it? Is there a workaround such that we can write a release note and fix it in Boron-SR2 instead?
Testing: Could you also elaborate on the testing of 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?

> Regression: Is this bug a regression of functionality/performance/feature compared to Boron (Build RC3.5)?

No it's not a regression, it was already present in Boron release.

> Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron-SR1 without it? Is there a workaround such that we can write a release note and fix it in Boron-SR2 instead?

Ah maybe it could be release note instead of blocking the release. There is a know workaround, as explained in the comment of this BUG.

> Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?

Manuel testing were perform, the BUG is indeed fix by the patches.

> Impact: Does this fix impact any dependent projects?

This fix impact l2switch project, as it allows the project to load its features in whatever order, instead of having to follow a precise order.

Has this bug been verified as fixed in the latest Boron SR1 Build 20161030?

@An - I cross checked it against https://www.opendaylight.org/software/downloads/boron-sr1 and the issue is resolved.

Below is the link of karaf log which shows the bundle initialization is resolved when following features are installed in order, but there is an abnormal Info message "about Unable to create a proxy object".

Installed bundles in order:-
odl-l2switch-switch
odl-dlux-node

Link:- https://gist.github.com/SaiSujithReddy/ba74e82accea3b40c73b54f755f18b4c

Installed bundles in order:-
odl-l2switch-switch-ui

Link:- https://gist.github.com/SaiSujithReddy/eb8abef58f39bff61ac8d95c592d1837