Last Modified: Jul 28, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Known Affected Versions:
2.2.1, 2.2.2, 2.2.3
Opened: Feb 27, 2026 Severity: 2-Critical
While upgrading from BNK 2.2.0 to 2.2.1 using the F5 Lifecycle Orchestrator (FLO), the DSSM upgrade hook pod gets stuck in a `container-creating` state, preventing the DSSM pods from upgrading successfully.
The DSSM DB pods are not upgraded to the latest version.
This issue is observed when upgrading from BNK 2.2.0 to 2.2.1 using FLO.
Before the upgrade, create a file named `dssm-upgrade-cm.yaml` containing the configuration for the `ConfigMap` in the lower version prior to performing the upgrade. ```yaml apiVersion: v1 kind: ConfigMap metadata: name: f5-dssm-logs-config data: .minlevel.yaml: | ``` Apply the `dssm-upgrade-cm.yaml` in the same namespace where the DSSM pods are deployed. ```shell kubectl apply -f dssm-upgrade-cm.yaml -n <dssm pods installed name space>
None