Bug ID 2277317: Problematic "Pending" tenants need to be called out on the Tenant Deployments screen

Last Modified: Oct 19, 2026

Affected Product(s):
F5OS F5OS-A, F5OS-C(all modules)

Known Affected Versions:
F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3, F5OS-A 1.8.4, F5OS-A 1.8.4-HR1, F5OS-A 1.8.4-HR2, F5OS-A 1.8.4-HR3, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2, F5OS-C 1.8.2-HR1, F5OS-C 1.8.2-HR2, F5OS-C 1.8.2-HR3

Opened: Apr 14, 2026

Severity: 3-Major

Symptoms

Tenants that are in the "Pending" state due to an error need to be called out better on the "Tenant" Deployments" screen in the GUI.

Impact

Confusion as to why a tenant seems to be stuck in the "Pending" state.

Conditions

Deploying an undeployable tenant.

Workaround

Look on the "Tenant Details" screen of the problematic tenant. Or use one of the options detailed in K70034058.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips