Operating System: All
Platform: All

Merging only portion of patches providing clustering support in stable/boron resulted to blocker bug (one not cluster aware module is failing to start because of dependency on already cluster aware module). Theres need for either unlock boron for merging additional 9 patches or to revert 4 already merged patches.

Clustering singleton service for GBP actually contains 13 patches

Merged:
https://git.opendaylight.org/gerrit/#/c/44862/
https://git.opendaylight.org/gerrit/#/c/44971/
https://git.opendaylight.org/gerrit/#/c/44972/
https://git.opendaylight.org/gerrit/#/c/44973/

Unmerged:
https://git.opendaylight.org/gerrit/#/c/45149/3
https://git.opendaylight.org/gerrit/#/c/45150/3
https://git.opendaylight.org/gerrit/#/c/45154/3
https://git.opendaylight.org/gerrit/#/c/45155/3
https://git.opendaylight.org/gerrit/#/c/45201/2
https://git.opendaylight.org/gerrit/#/c/45202/2
https://git.opendaylight.org/gerrit/#/c/45203/2
https://git.opendaylight.org/gerrit/#/c/45204/2
https://git.opendaylight.org/gerrit/#/c/45205/2

Is required either to revert 4 merged patches or merge 9 remaining.

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron without it? Is there a workaround such that we can write a release note and fix in future Boron SR1?
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?

Tested and verified, issue with installing of GBP features no longer appears