Bug ID 1297521: Full sync failure for traffic-matching-criteria with port list update on existing object in certain conditions

Last Modified: Mar 30, 2024

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

Opened: May 10, 2023

Severity: 4-Minor

Symptoms

Performing a full configuration sync with traffic-matching-criteria (TMC) under specific conditions fails with errors similar to: err mcpd[5781]: 01070710:3: Database error (13), Cannot update_indexes/checkpoint DB object, class:traffic_matching_criteria_port_update status:13 - EdbCfgObj.cpp, line 127. err mcpd[5781]: 01071488:3: Remote transaction for device group /Common/HA to commit id 41 failed with error 01070710:3: Database error (13), Cannot update_indexes/checkpoint DB object, class:traffic_matching_criteria_port_update status:13 - EdbCfgObj.cpp, line 127..

Impact

Unable to sync configurations.

Conditions

This may occur on a full-load config sync (not an incremental sync) Both Active and Standby on sync already - a traffic-matching-criteria is attached to a virtual server - the traffic-matching-criteria is using a port-list - Update the port list (Add new port in the existing list) Ex: tmsh modify net port-list /Common/<> { ports replace-all-with { 80 { } 83 { } 84 { } } port-lists none } Assume port list already with 80,83 and adding new port 84 in the list. NOTE: No issue observed when we try to update the list with removing the port from the list.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips