Description of problem: When a user tries to delete a non existing access rule under it's scope, it deletes by accident it's other existing access rule which are not associated with any application credentials, under his scope. Version-Release number of selected component (if applicable): Reproducible in 17.0 and in 17.1. How reproducible: Steps to Reproduce: 1.Create a user or use the default admin role 2.Create an application credentials with access rule. 3.Delete the application credentials, not the access rule. 4.List the access rule - It should be found there. 5.Try to delete access rule with a random name. 6.List again the access rule and see if it still there. Actual results: The access rule was deleted , although the request didn't requested to delete it. Expected results: The access rule should still appear in the list. Additional info:
*** Bug 2245163 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat OpenStack Platform 17.1 (python-openstackclient) security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:2737