Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Fixed In:
1.7.9
Opened: Jul 08, 2024 Severity: 1-Blocking
Currently, in SPK, if the RabbitMQ pod is down, the CWC pod is in a "Ready" state, even though the connection between CWC and RabbitMQ is broken.
License status not getting updated in RabbitMQ.
1. Random start up of RabbitMQ pod & multiple restarts of RabbitMQ can cause the issue. 2. Stop the RabbitMQ Pod
Restart CWC pod.
The Readiness Probe/Liveness Probe will check the server running in the CWC pod. The server will be up only when the connection between CWC and RabbitMQ is established and the queue is generated. If any of these conditions fail, the server will stop running, resulting in a readiness/liveness probe failure. Restarting the CWC pod will allow the server to start once the connection is re-established, and the CWC pod will transition to the "Ready" state.