Last Modified: Jun 25, 2026
Affected Product(s):
F5OS F5OS, F5OS-A, F5OS-C
Known Affected Versions:
F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.5.4, F5OS-A 1.8.3, F5OS-A 1.8.4
Opened: May 13, 2026 Severity: 3-Major
On F5OS-A systems, kubelet may continuously log errors similar to the following every ~2 seconds: orphaned pod "<pod-uuid>" found, but failed to remove volume at path /var/lib/kubelet/pods/<pod-uuid>/volumes/kubernetes.io~configmap/<tenant>-configmap: remove ...: directory not empty This log flood occurs when the kubelet is unable to clean up the configmap volume directory for an orphaned tenant pod
-- Continuous error log messages in /var/log/messages (approximately one every two seconds) -- No functional impact to running tenants; the issue is cosmetic/operational (log noise) -- Manual intervention may be required to clean up the stale directory
-- F5OS-A version 1.5.x or 1.8.x (including 1.8.3) on rSeries platforms -- The tenant pod is orphaned after a reboot (old pod replaced by a new pod for the same tenant) -- The configmap volume directory for the old pod retains its standard Kubernetes content (timestamped data subdirectory, ..data symlink, and key symlinks)
Manually delete the stale configmap directory for the orphaned pod using standard Linux file removal commands (e.g., rm -rf) Note: Ensure the directory is not in use by any active pod before removal
None