Bug ID 2690357: Config sync fails after AS3 tenant partition deletion - partition objects not removed from Standby device

Last Modified: Oct 22, 2026

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

Known Affected Versions:
21.1.0.2, 21.1.0.3

Opened: Oct 16, 2026

Severity: 3-Major

Symptoms

After deleting an AS3 tenant partition on the Active device in an HA pair, config sync fails with the following error: 0107082a:3: All objects from local device and all HA peer devices must be removed from a partition (<partition_name>) before the partition may be removed, type ID (2070), text ID (270275)

Impact

- Config sync between Active and Standby enters a persistent "Sync Failed" state - Configuration changes made on the Active device after the failure will not be synchronized to the Standby - The Standby device retains stale objects from the deleted partition

Conditions

- BIG-IP version 21.1.0.x in an HA pair (sync-failover device group) - AS3 used to manage tenant partitions containing LTM objects - AS3 tenant partition is deleted (via AS3 DELETE declaration or empty tenant declaration) - Large or complex configuration with multiple partitions and high object count (e.g., 2900+ virtual servers, 40+ partitions)

Workaround

Manually delete the orphaned partition objects on the Standby device, then re-sync: Step 1: On the Standby device, list remaining objects in the partition: tmsh list /<partition_name>/ recursive Step 2: Delete objects in dependency order on the Standby: tmsh delete ltm virtual /<partition_name>/ recursive tmsh delete ltm pool /<partition_name>/ recursive tmsh delete ltm snatpool /<partition_name>/ recursive tmsh delete ltm snat-translation /<partition_name>/ recursive tmsh delete ltm profile client-ssl /<partition_name>/ recursive tmsh delete ltm persistence /<partition_name>/ recursive tmsh delete ltm monitor /<partition_name>/ recursive Step 3: Delete the partition on the Standby: tmsh delete auth partition <partition_name> > Note: If Step 3 fails with the same "0107082a" error, run "tmsh list /<partition_name>/ recursive" again to identify any remaining objects (e.g., nodes, SNAT translations, other profiles) and delete them individually before retrying. Step 4: Re-sync from Active: tmsh run cm config-sync to-group <device_group_name> Step 5: Verify on both devices: tmsh show cm sync-status After applying the workaround, monitor sync status following any future AS3 partition deletions until a fix is available.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips