Last Modified: May 23, 2026
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Fixed In:
1.9, 1.7.2, 1.7
Opened: Apr 28, 2023 Severity: 3-Major
The SPK DSSM deployment might go into an inaccessible or erroneous state under certain scenarios.
Inaccessible or erroneous state for SPK DSSM deployment. In this state no data is written and lookup operations are not available.
This state can get triggered if the DB/Sentinel Pods are reassigned their IP addresses. Reasons for reasssignment could include operations like DB/Sentinel Pod recreation or deletion.
None
This fix addresses the DB/Sentinel Pod’s auto recovery capability to respond to the scenarios it needs to address. This fix also introduces additional logging to get more information for unforeseen issues like this.