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.
I noticed that after I deploy Satellite 6.2 in default configuration and
click on Mistmatched reports, I get the default Org and Loc in the
result. That means the Log does not belong into the Org.
I noticed this in 6.1 as well (not sure about 6.0).
https://postimg.org/image/7y78i3myn/
What you mean where? Have you noticed the image? https://postimg.cc/image/7y78i3myn/
It's in Org/Loc - Mismatches report. Standard installation (default options).
Yes, of course I looked at your screenshot but it doesn't have any indication what page you're looking at or how to get there. On my fresh Satellite 6.2 install, I do not have any mismatches when I go to Manage Organizations, and click the Mismatches button in the upper right corner.
Perhaps I was wondering if I am looking in the wrong place. The taxonomies UI is a confusing labyrinth of switches and buttons, with several things that offer to show/fix mismatches.
On another 6.2 box I see it, not sure why mine doesn't have it. Anyway, these are created by Foreman's db:seeds, so it should do the right thing by associating the default org/location with each other. Changing the category out of the installer.
The way this works is rather confusing, this "feature" of adding an Organization to a Location or a Location to an Organization is meaningless, everything works regardless of whether you do this or not.
I wish I could confirm that everything works, but I was running into various issues. I can't remember the BZs tho at the moment, let's keep this as low prio for the record. Thanks for analysis.