Loading...
Loading...
When you create API per-request policy using the same name as a policy from another partition, BIG-IP generates an error similar to the following: java.net.ProtocolException: status:400, body:{"code":400,"message":"transaction failed:01070734:3: Configuration error: DB validation exception, unique constraint violation on table (subroutine_properties) object ID (/TST/svc1-my_auth svc1-my_prp). A duplicate value was received for a non-primary key unique index field. DB exception text (Cannot update_indexes/checkpoint DB object, class:subroutine_properties status:13)","errorStack":[],"apiError":2}.
Import / export functionality fails.
-- Configure an API protection per-request policy in one partition with the same name as a policy in another partition. -- Attempt to import or export the policy.
Ensure that names for API protection per-request policies are unique.
The name generated for API protection per-request policies now uses partition name combined with the policy name, so the issue no longer occurs.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.