Bug ID 2501837: F5OS 2.0 BIG-IP 21.1 tenant deployment failed when using cloud-init tmos_declared module

Last Modified: Oct 06, 2026

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
21.1.0, 21.1.0.1, 21.1.0.2

Opened: Sep 03, 2026

Severity: 3-Major

Symptoms

When provisioning BIG-IP TMOS 21.1 on F5OS 2.0 using cloud-init, the tmos_declared module fails. The cloud-init log contains the following error: IOError: [Errno 2] No such file or directory: '/root/.ssh/authorized_keys'

Impact

Cloud-init provisioning through tmos_declared fails, preventing completion of the module's onboarding tasks, including configured post-onboarding commands

Conditions

This issue occurs when cloud-init runs with tmos_declared enabled and the module attempts to access the SSH authorized keys file before the network service has completed SSH key setup The issue has been observed with BIG-IP TMOS 21.1 on F5OS 2.0

Workaround

Add the following bootcmd block to the cloud-init configuration to wait for system readiness before the tmos_declared module executes: bootcmd: - source /usr/lib/bigstart/bigip-ready-functions; wait_bigip_ready

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips