Red Hat Bugzilla – Bug 1300336
CFME 4.0 session setting necessary for proper CFME operation in Load Balancer environment is no longer acceptable and causes worker failures
Last modified: 2016-02-10 10:36:06 EST
http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/735
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=6fe7f5f659e8e2ed403f0383b48233c260f8d56b commit 6fe7f5f659e8e2ed403f0383b48233c260f8d56b Author: Nick Carboni <ncarboni@redhat.com> AuthorDate: Tue Jan 19 17:07:13 2016 -0500 Commit: Nick Carboni <ncarboni@redhat.com> CommitDate: Wed Jan 20 08:53:00 2016 -0500 Added the activerecord-session_store gem As of https://github.com/rails/rails/commit/0ffe19056c8e8b2f9ae9d487b896cad2ce9387ad the session store was extracted into a gem. We need it for the `session_store: sql` functionality. Clean cherry-pick from upstream master Upstream PR: https://github.com/ManageIQ/manageiq/pull/6255 https://bugzilla.redhat.com/show_bug.cgi?id=1300336 Gemfile | 1 + 1 file changed, 1 insertion(+)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=882deeef2df94a90fa751d6021d690b1374391c6 commit 882deeef2df94a90fa751d6021d690b1374391c6 Merge: d706d0c 6fe7f5f Author: Gregg Tanzillo <gtanzill@redhat.com> AuthorDate: Wed Jan 20 09:42:11 2016 -0500 Commit: Gregg Tanzillo <gtanzill@redhat.com> CommitDate: Wed Jan 20 09:42:11 2016 -0500 Merge branch 'backport_activerecord_session_store_gem' into '5.5.z' Added the activerecord-session_store gem As of https://github.com/rails/rails/commit/0ffe19056c8e8b2f9ae9d487b896cad2ce9387ad the session store was extracted into a gem. We need it for the `session_store: sql` functionality. Clean cherry-pick from upstream master Upstream PR: https://github.com/ManageIQ/manageiq/pull/6255 https://bugzilla.redhat.com/show_bug.cgi?id=1300336 See merge request !735 Gemfile | 1 + 1 file changed, 1 insertion(+)
5.5.2.2.20160121120249_395c086
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/RHBA-2016:0159