Bug ID 675319: Multiple client-policy objects can be added to a connectivity profile using TMSH

Last Modified: Dec 20, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jul 24, 2017
Severity: 3-Major

Symptoms

Using the following command makes it possible to add a client policy to a connectivity profile even if it already has one. However, each connectivity profile should only have one client policy. tmsh modify apm profile connectivity MyConnectivityProfile client-policy add { ThisDoesntExist {} }

Impact

The presence of the additional client-policy in a connectivity profile causes the config to have an error on loading.

Conditions

Using TMSH to modify the connectivity profile.

Workaround

Do not modify the connectivity profile to add client-policy.

Fix Information

Now there will be an error if you attempt to modify a connectivity profile to have more than one client-policy.

Behavior Change