Bug ID 1567945: QAT entries for the deleted tenant still show up in cluster

Last Modified: Jun 30, 2025

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

Known Affected Versions:
F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.7.0

Fixed In:
F5OS-A 1.8.0

Opened: Mar 21, 2024

Severity: 3-Major

Symptoms

When a tenant is deleted and a reboot scenario such as a live upgrade is performed, a reference to the deleted tenant remains in the cluster via ConfD and internally in qat-support-pod.

Impact

Incorrect reporting through ConfD.

Conditions

Deletion of a tenant occurs just before a reboot.

Workaround

None

Fix Information

A monitor checks for changes to tenant configurations. Upon detecting deletion or un-deployment, the qat-devs.json file is promptly updated. Subsequently, the tenant is marked as terminated, thereby notifying the informer to refrain from updating device records with outdated values.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips