Last Modified: Nov 29, 2025
Affected Product(s):
BIG_IP_NEXT(CNF) CNF
Fixed In:
1.4.0
Opened: Mar 15, 2024 Severity: 1-Blocking
During upgrade of CWC on Robin environment using helm upgrade the new CWC is getting stuck in `ContainerCreating` state. The issue was because, the old pod of CWC is not releasing the PVC and hence the new pod is not coming up as the PVC is already occupied by the old CWC pod. Its getting stuck due to Multi-Attach error for volume as volume is already used by pod(s).
New CWC pod gets stuck forever in ContainerCreating state. Which means that the upgrade is not succeeded
Upgrading CWC on robin environment using `helm upgrade` command
1. Uninstall CWC when the container gets stuck in `ContainerCreating` state while upgrading 2. Wait till the pod gets removed completely 2. Install CWC with the new version
Using Recreate Strategy instead of rollingUpdate on robin env for CWC Please note that this change is only applicable for Robin Environment. To get these new strategy changes working you need to set a new environment variable in the following way: `--set clusterEnv.Robin=true` in installation/upgrade command while installing/updating the CWC. Also, if you do a rollback to the previous version that does not have this change. The rollback happens in rollingUpdate way, which is anticipated, and you might face the issue of CWC getting struck in `ContainerCreating` state. In such case you have to follow the below steps 1. Uninstall CWC 2. Wait till the pod gets removed completely 2. Install CWC with the rollback version