Bug ID 677148: Periodic content insertion creates duplicate records if same policy is added to Global high and subscriber specific

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP PEM(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, 12.1.4.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5

Fixed In:
14.0.0, 13.1.0.6

Opened: Aug 04, 2017
Severity: 3-Major

Symptoms

If same pem policy with insert content is added to global high and subscriber specific, insert content could add duplicate records. This result in a case where if the periodic content tag is absent, the periodic content insertion will not scheduled immediately, but will add only after the expiry of the current interval.

Impact

if the periodic content tag is absent, the periodic content insertion will not scheduled immediately.

Conditions

If same pem policy with insert content is added to global high and subscriber specific.

Workaround

This is a wrong configuration, a pem policy should be included either in Global High, or subscriber specific, not both.

Fix Information

Re-use the already created record in case of same policy attached to Global high and subscriber specific

Behavior Change