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:

Organization id accepts location ids without any error and vice versa. It seems to be a cross-api problem in the taxonomized resources.


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 (or any other taxonimized resource) via api and set organization_ids field to the location id from the previous step
3. The api call accepts the wrong id
4. Check details of the just created user. It will have blank organizations but locations will be set to the one form the step 1.


Actual results:
It silently assigns location instead of organization.


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


Additional info:
We store taxonomies (organizations and locations) into the same db table. API controllers probably don't check their types.

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.