Bug ID 1297913: DSSM Pods do not go for reboot post upgrade, however upgrade is declared successful

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(SPK) SPK(all modules)

Fixed In:
1.9

Opened: May 11, 2023

Severity: 3-Major

Symptoms

If the f5-dssm-store version does not change, all the pods do not get restarted post-upgrade.

Impact

If the helm chart has changed, the pods do not restart and may not get the latest changes with the new version.

Conditions

Upgrade dssm, without a version change in the f5-dssm-store image. This is an unlikely scenario, as every release will have changes to the f5-dssm-store version.

Workaround

None

Fix Information

Post upgrade, all the DB and Sentinel pods are restarted.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips