Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
A user, even admin, can not edit their own taxonomies.
Version-Release number of selected component (if applicable):
6.2.10
How reproducible:
always
Steps to Reproduce:
1. Create a new user with no taxonomies assigned.
2. Login as the new user and edit own account.
3. Add a location or organization
4. Save user
5. Edit own account again - note the organization/location was not saved
Actual results:
Organization/Location change is not saved
Expected results:
Organization/Location change is saved
Additional info:
This seems to work in upstream develop correctly.
Even simpler reproducer:
1. Log in as admin
2. Try to edit own taxonomies (add/remove a location/organization on your account)
3. Save
You will see the save succeed, but going into editing account again you will see the change was not preserved.
Verified in Satellite 6.2.15 Snap 2.
Created a new organization and location.
Edited the main admin account to align them.
Saved the config.
Reloaded the edit user page for the admin account.
The orgs and locations were aligned correctly.
Created a new account with admin privileges and no orgs or locations aligned.
Signed in to the new account, being presented with the edit user page.
Aligned the new org and default location to the user.
After logging back in to the test user, the new org and default location were aligned correctly.
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, 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/RHBA-2018:1672
Comment 20milesjr
2023-03-25 14:48:37 UTC
Comment hidden (spam)
This comment was flagged a spam, view the edit history to see the original text if required.
Comment 21mary45
2023-08-22 09:45:40 UTC
Comment hidden (spam)
This comment was flagged a spam, view the edit history to see the original text if required.