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:

When accessing the Satellite WebUI from Firefox on Android, it's not possible to change the currently selection organization or location.

The menu showing the current location/org and the "Manage Organizations" and "Manage Locations" links appears, but touching the listed location just reselects the current location, there doesn't appear to be any way of bringing up the list of locations to select a new one.

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

Not sure how to determine this.

How reproducible:

100%

Additional info:

Haven't yet checked if this also occurs with Chrome or other Android browsers.

Created redmine issue http://projects.theforeman.org/issues/7546 from this bug

This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.