Last Modified: Apr 20, 2022
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.4, 188.8.131.52, 13.1.5
Opened: Aug 15, 2017
The existing error message when deleting an access policy that is owned by an access profile is not descriptive: 01071111:3: Cannot delete access policy (/Common/delete_me_access_profile) because it is owned by a profile. It does not specify which profile owns the access policy.
This makes it difficult to debug, because the message does not state which access profile owns the access policy.
When you try to delete an access policy owned by an access profile from tmsh using a command similar to the following: delete apm policy access-policy delete_me_access_profile
Manually check the access profiles to see which profile owns the access policy.
The tmsh error message for deleting APM policy access-policy has been updated to include the name of the access profile that owns it.