Bug ID 1634109: Instance Creation Failed for rSeries 2k and 4k

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(CM) F5OS-A, Install/Upgrade(all modules)

Fixed In:
20.3.0

Opened: Aug 27, 2024

Severity: 3-Major

Symptoms

Trying to create a BIG-IP Next tenant on rSeries 2k and 4k fails.

Impact

Unable to create a BIG-IP Next instance. The tenant will not be deleted by Central Manager.

Conditions

Trying to create a BIG-IP Next tenant on rSeries 2k and 4k. The logs indicates that "there are containers with unready status".

Workaround

When creating instance in rSeries 2k and 4k, In the Instance Creation wizard, under the "Troubleshooting" tab, select "1200" in the "Timeout (seconds)" dropdown.

Fix Information

Selecting the Timeout to be 1200 when creating instance from CM for rSeries 2k and 4k

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips