Gateway service won't start after upgrade 11.0

Products

• CA API Gateway

Issue/Introduction

In the gateway 11.0 SSG logs.

2023-10-12T13:56:38.769-0400 SEVERE  138 com.hazelcast.security: [my.ip.addr]:8777 [gateway] [5.1.1] Node could not join cluster. Before join check failed node is going to shutdown now!
2023-10-12T13:56:38.770-0400 SEVERE  140 com.hazelcast.security: [my.ip.addr]:8777 [gateway] [5.1.1] Reason of failure for node join: Joining node's version 5.1.1 is not compatible with cluster version 5.2 (Rolling Member Upgrades are only supported for the next minor version) (Rolling Member Upgrades are only supported in Hazelcast Enterprise)
.... Removed ....

com.l7tech.server.LifecycleException: Lifecycle error: Could not initialize Hazelcast cluster
        at com.l7tech.server.LifecycleExtensionComponent.start(Unknown Source)
        at com.l7tech.server.BootProcess.start(Unknown Source)
        at com.l7tech.server.boot.GatewayBoot.f(Unknown Source)
        at com.l7tech.server.boot.GatewayBoot.start(Unknown Source)
        at com.l7tech.server.boot.GatewayBoot.runUntilShutdown(Unknown Source)
        at com.l7tech.server.boot.GatewayMain.main(Unknown Source)
Caused by: com.ca.apim.gateway.extension.lifecycle.LifecycleException: Could not initialize Hazelcast cluster
        at com.l7tech.external.assertions.hazelcastembeddedprovider.server.a.start(Unknown Source)
        ... 6 more
Caused by: java.lang.IllegalStateException: java.lang.IllegalStateException: Node failed to start!
2023-10-12T13:56:39.809-0400 WARNING 1 STDERR: com.l7tech.server.LifecycleException: Lifecycle error: Could not initialize Hazelcast cluster

Environment

Release : 11.0

Resolution

This type of problem is a library Version mismatch. For example if you installed 11.0 CR01 on 1 node and  the other node was 11.0 base which caused a Hazelcast mismatch. Please ensure all running nodes are running the same gateway version and CR.