Fix OpsManager registry instantiation 91/89991/1
authorRobert Varga <robert.varga@pantheon.tech>
Wed, 3 Jun 2020 13:51:54 +0000 (15:51 +0200)
committerRobert Varga <nite@hq.sk>
Wed, 3 Jun 2020 13:56:28 +0000 (13:56 +0000)
commit47a9c289471aac2ae5027932178ccd1c77fd31fe
treef2a84c2bc995087c9dfcbdb9de855c3664526503
parent384828e93c43de246e272a6fd640ff7717a4acfa
Fix OpsManager registry instantiation

We have a day-zero bug with actions, as OpsManager ends up
instantiating the wrong actor -- hence we have two RpcRegistry
instances and no ActionRegistry instances.

JIRA: CONTROLLER-1943
Change-Id: I3b374454af3225cf13d5e23e4fb6744bf3f9ed99
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
opendaylight/md-sal/sal-remoterpc-connector/src/main/java/org/opendaylight/controller/remote/rpc/OpsManager.java