Fix OpsManager registry instantiation 92/89992/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:37 +0000 (13:56 +0000)
commit8eb3df3d4dfdb087344cb269cdddc4b723266537
treed362aba5b8501603f5e579219c1cbce863292906
parent596d083fe41862ac08fb08cd4b3567a4f9a482ee
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