Fixed error when uploading CBA when Hazelcast cluster is not initialized 78/120978/3
authorJulien Fontaine <julien.fontaine@bell.ca>
Wed, 20 Jan 2021 23:28:49 +0000 (18:28 -0500)
committerJulien Fontaine <julien.fontaine@bell.ca>
Wed, 28 Apr 2021 21:20:37 +0000 (17:20 -0400)
commit7727db93b8c157e3b6e563c1f8093f8eddd9ad5a
treee618dc8bf4c4457b904992727dc48a70dbd175d4
parentbfca233b96801b53af015f3532fa73c615fef6e4
Fixed error when uploading CBA when Hazelcast cluster is not initialized

Hazelcast is used to enable CDS pods to notify the rest of the CDS cluster when a CBA got updated locally so they clean their compile cache (if they have an entry for that CBA). Though, the code doesn't make sure that hazelcast cluster is fully initialized before trying to notify using a hazelcast topic.
Fixed that error by making sure that the cluster is fully initialized before pushing notification to hazelcast topic.

Issue-ID: CCSDK-3277
Change-Id: I44211c63c5a991269005bcc238f18b19979cb718
Signed-off-by: Julien Fontaine <julien.fontaine@bell.ca>
ms/blueprintsprocessor/modules/commons/db-lib/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/db/primary/service/BlueprintProcessorCatalogServiceImpl.kt