Bug ID 1209669: BIG-IP Next fails to come up intermittently upon system power cycle/reboot

Last Modified: May 29, 2024

Affected Product(s):
F5OS F5OS(all modules)

Fixed In:
F5OS-C 1.6.0

Opened: Dec 14, 2022

Severity: 3-Major


Every tenant gets its own storage space and F5OS applies the right permissions for BIG-IP Next to access the necessary paths to generate certs/database/etc. When the system goes for a reboot, F5OS will have to remount the storage path from volume. But when it does, F5OS is skipping those permissions back, hence tenant containers are failing to access the path and go for a crash loop.


The tenant will not be available functionally or pass any traffic since the majority of containers are in the restart loop due to permission issues.


When the system goes for power cycle or blade reboot.


Please run the following commands from the blade shell setfacl -Rdm u:7053:rwx /mnt/disks/<tenant-name>/ setfacl -Rm u:7053:rwx /mnt/disks/<tenant-name>/

Fix Information

Containers and pods.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips