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:
on a clean installation, web UI sessions are reset after every single request.
This appears to be caused by an idle_timeout set to zero.
As a workaround, go to Administer > Settings > General and set idle_timeout to 60 or similar.
Version-Release number of selected component (if applicable):
rpm -q foreman katello-installer katello
foreman-1.7.0.0-1.2.el6_6sat.noarch
katello-installer-2.1.1-1.el6_6sat.noarch
katello-2.1.0-1.el6_6sat.noarch
How reproducible:
One el6 smoketest host so far
Steps to Reproduce:
1. install RHEL 6.6
2. yum -y install katello
3. katello-installer
Actual results:
Attempting to log in results in repeated Session Expired messages.
Expected results:
Installation completes successfully and user is able to log in
Additional info:
Issues did not present themselves on the RHEL 7 smoketest host.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2015:1592