Last Modified: Oct 08, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9
Opened: Oct 01, 2026 Severity: 3-Major
After rebooting a BIG-IP VE system on Azure, the REST endpoint `/mgmt/shared/identified-devices/config/device-info` returns `"slots": []` despite the active software volume being healthy and complete. This prevents AS3 and other automation tools from identifying the active software slot. The following error is returned when attempting AS3 operations: {"code":400,"message":"patch operation failed - see logs for details. target device has no active slots"}
- AS3 operations fail - PATCH, deploy, and declaration operations return HTTP 400 after every reboot, blocking all AS3-driven automation - Automation workflows broken - Any workflow that depends on the device-info `slots` field (AS3, F5 Terraform provider, BIG-IQ discovery, custom REST automation) fails until restjavad is manually restarted
- BIG-IP Virtual Edition deployed on Microsoft Azure - 16 vCPUs (higher vCPU counts may increase I/O contention during boot) - BIG-IP v17.5.1.8 (Engineering Hotfix 0.158.19); may also affect other 17.x versions on cloud platforms - Multiple modules provisioned at nominal: LTM + ASM + AFM (heavy boot-time I/O from module initialization) - A full system reboot is required to trigger (restjavad-only restart does not trigger the issue)
Workaround after each reboot: bigstart restart restjavad && sleep 30 && bigstart restart restnoded Verify slots are populated: restcurl shared/identified-devices/config/device-info | python -m json.tool | grep -A5 slots
None