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:
API for creating users silently ignores location ids passed into default_organization_id and vice versa. No error is shown.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. List locations in the system, pick some id
2. Create a user via API, set default_organization_id to the value from the previous step
3. The user gets successfully created
4. Check details of the just created user. The default organization is blank.


Actual results:
It silently ignores the wrong id.


Expected results:
The call should return "Organization not found" error.


Additional info:

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1218929

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Moving 6.2 bugs out to sat-backlog.

Moving 6.2 bugs out to sat-backlog.

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.