Bug 2209607 - When a user tries to delete a non existing access rule, it deletes by accident another existing access rule in it's scope [NEEDINFO]
Summary: When a user tries to delete a non existing access rule, it deletes by acciden...
Keywords:
Status: POST
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 17.1
Assignee: Douglas Mendizábal
QA Contact: Jeremy Agee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-24 08:38 UTC by MilanaLevy
Modified: 2023-08-11 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
ifrangs: needinfo? (dmendiza)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 888697 0 None MERGED Fix "access rule" commands to only use ID 2023-07-18 17:00:07 UTC
Red Hat Issue Tracker OSP-25338 0 None None None 2023-05-24 08:39:11 UTC

Description MilanaLevy 2023-05-24 08:38:23 UTC
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:


Note You need to log in before you can comment on or make changes to this bug.