Bug ID 439363: Auto-generated policy names might be too long

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, Install/Upgrade, LTM, WAM(all modules)

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9

Fixed In:
11.6.0, 11.5.2, 11.4.1 HF9

Opened: Dec 02, 2013
Severity: 3-Major
Related AskF5 Article:
K15112

Symptoms

Auto-generated policy names might be too long for the system to handle. When you load a configuration, the system combines multiple HTTP Class profiles names into a single local traffic policy before assigning it to a virtual server.

Impact

Upgrades and UCS restores fail. The mcpd process fails to load configuration and logs an error the /var/log/ltm file: 0107141f:3: The maximum allowable length of 255 for a full path has been exceeded. The object name was auto-generated-policy-name), the truncated folder path was /foldername/truncated-auto-generated-policy-name). Unexpected Error: Loading configuration process failed.

Conditions

When the local traffic policy name exceeds the maximum allowable length, the mcpd process fails to load the upgraded configuration.

Workaround

Shorten the names of the HTTP Class profiles before upgrade.

Fix Information

When the local traffic policy name that is auto-generated from multiple HTTP Class profile names is longer than the maximum supported length of 255 characters, the system now truncates the name, so that config load and upgrade occur successfully.

Behavior Change