Bug ID 1113889: Classic BIG-IP tenant running on F5OS will not correctly pin in-tenant control plane threads correctly on first deployment

Last Modified: Mar 30, 2024

Affected Product(s):
BIG-IP vCMP(all modules)

Fixed In:
17.1.0, 15.1.9

Opened: Jun 13, 2022

Severity: 4-Minor

Symptoms

This may not impact performance in the tenant, but for tenant builds without this fix, upon initial deployment, the control plane will not be pinned correctly (should be pinned to odd-numbered cpus). Note: This pinning is inside the tenant virtual machine, not in the F5OS host. The datapath (TMM) will still be pinned correctly.

Impact

The datapath (TMM) threads run at elevated priority anyway, so would be protected from the control plane threads.

Conditions

The BIG-IP tenant without this fix is initially deployed.

Workaround

If this is bothersome, redeploy the tenant, and the problem will not reoccur.

Fix Information

Tenant platform determination no longer depends on a file that is not there on initial startup. The dmidecode utility is used instead.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips