Bug ID 1137121: Tenants are stuck in Pending state with status 0/1 nodes available after upgrading to F5OS-A 1.2.0

Last Modified: Aug 01, 2024

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

Fixed In:
F5OS-A 1.7.0, F5OS-A 1.5.0, F5OS-A 1.4.0, F5OS-A 1.3.0

Opened: Aug 17, 2022

Severity: 2-Critical

Symptoms

The system is unable to start tenants, and the tenant reports a status of "Insufficient f5.com/qat".

Impact

Tenants will not start and are unusable.

Conditions

Might occur after an F5OS-A software upgrade or after reinstalling K3s.

Workaround

To work around this issue, perform one of these actions: 1. Reboot the rSeries appliance. or 2. Restart the qat-plugin process by logging into the appliance as root, and running "pkill qat-plugin".

Fix Information

Fixed an issue with the qat-plugin process that prevented the system from starting tenants.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips