Description of problem: >> User is not able to create or view locations when assigned a cloned role for "Organization Admin" even when its filters have "create location" field added by default. Version-Release number of selected component (if applicable): >> 6.4.0 How reproducible: 100% Steps to Reproduce: >> Clone the "Organization Admin" Role shipped by satellite and assign it to a user. >> Filters in the role for "Location" says that user should be able to create and view the locations. >> User is assigned to the appropriate location. Actual results: User not able to see or create a location Expected results: User should be able to create a new location. Additional info: N/A
I can see the locations, but the creating clearly doesn't work. It don't allow me to create it with error: "You don't have permission create_locations with attributes that you have specified or you don't have access to specified organizations or locations"
Created redmine issue https://projects.theforeman.org/issues/29012 from this bug
This clearly works in satellite 6.4, but doesn't work in upstream. Amaani could you please confirm what version have you tested this on? I've further noticed, that upstream while cloning the role, the unlimited flag in filters for the cloned role are unselected. There was a recent change in this flag seting, I'd susspect that could be the cause. The flag got unselected on clone and than the filter is used with an empty search, what would not work.
We've digged deeper into this and the actuall issue appears to be present only if user assigns the newly cloned role some locations. Than user with this role can manage only locations assigned to this role, so he can't create new one. That's actually correct behaviour, only bit unclear UX.
*** Bug 1760701 has been marked as a duplicate of this bug. ***
I've created https://bugzilla.redhat.com/show_bug.cgi?id=1825698 to track the real issue.
Based on comment 17, should I close this?
Yes, could you, I do not know how to properly reference the new BZ.
closing this based on comment 17.