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.
Created attachment 612533[details]
screenshot
Description of problem:
Version-Release number of selected component (if applicable):
Katello Version: 1.1.12-1.git.29.d796c20.el6_3
How reproducible:
Steps to Reproduce:
1. (assuming admin has no default org set, if he does, unset it and log out).
2. Go to login screen, enter admin/admin
3. Click Login
4. Reload the browser page (or enter https://servername/katello/ in address bar)
Actual results:
Taken to a dashboard page with no org selected, no tabs or anything else available.
Expected results:
Additional info:
I have automation screenshots of this behavior, where the main UI area (below the menu) shows a 403, but I can't reproduce the 403 message, only the no-org state. See attached screenshot
I cannot reproduce the 403, and I would argue that the behavior of landing on the dashboard with no organization selected is not a bug. This might be a usability issue, but a user is not required to have a selected organization to access the main application (even though if they don't, there is not much they can do other than see their profile and notifications).
I'd argue that this is a regression then, as the expected behavior was that a user should always have a "landing Organization" unless said user has no access yet configured.
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM. If this is a mistake feel free to re-open.