Last Modified: Jul 18, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Known Affected Versions:
2.2.0
Fixed In:
2.2.1
Opened: Jan 19, 2026 Severity: 3-Major
The controller lacks a reconciliation mechanism to retry status updates for previously failed CRs when the IPSD pod recovers. The status update logic only executes during initial CR creation/update or explicit CR modification events. When configuration delivery fails due to pod unavailability, the status is set to "Failed", but no automatic reconciliation is triggered to reassess and update the status once the IPS pod becomes operational again and configs are delivered to it successfully.
Users cannot determine the actual state of their configurations and use-case may appear misconfigured when they are actually functioning correctly. This is true for AFM, DWBLD, BDOSD and Downloader pods as well.
When configuration delivery to the IPS pod fails, F5BigIpsPolicy CR statuses are marked as "Failed". However, after the IPS pod becomes healthy, subsequent successful configuration deliveries do not trigger a status update on the affected CRs. The CRs remain in the "Failed" state despite the configurations being successfully applied to the IPS pod.
Users need to manually trigger CR reconciliation by performing a trivial update/re-create to the affected CRs to force the controller to re-evaluate and update the status. Or Users can restart the CNE controller pod.
None