Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1552245 - [OSP11] horizon stanza in haproxy.cfg needs tweaking
[OSP11] horizon stanza in haproxy.cfg needs tweaking
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo (Show other bugs)
11.0 (Ocata)
Unspecified Linux
medium Severity medium
: z5
: 11.0 (Ocata)
Assigned To: Michele Baldessari
pkomarov
: Triaged, ZStream
Depends On: 1485446
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-06 14:50 EST by Michele Baldessari
Modified: 2018-05-18 13:04 EDT (History)
15 users (show)

See Also:
Fixed In Version: puppet-tripleo-6.5.10-2.el7ost
Doc Type: Bug Fix
Doc Text:
Cause: Previously the cookie being inserted by haproxy into the response was not dependent on the backend server that replied. Consequence: This might have caused a subsequent connection to end up on a server that had no knowledge of the previous cookie, making a relogin necessary. Fix: Now the cookie inserted matches the backend server that replied. Result: The connection will always go to the same backend server
Story Points: ---
Clone Of: 1485446
Environment:
Last Closed: 2018-05-18 13:03:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 546995 None stable/ocata: MERGED puppet-tripleo: Give horizon's stanza in haproxy a per-server cookie (Ieb9cf3c6a8373df288a73ff2dacfc9d0b09e675a) 2018-04-09 13:27 EDT
OpenStack gerrit 550233 None stable/ocata: MERGED puppet-tripleo: Fix ipv6 horizon haproxy endpoint (If25fab0cf925cd5d2c003aa99f0aa9110dacd2ff) 2018-04-09 13:27 EDT
Red Hat Product Errata RHSA-2018:1627 None None None 2018-05-18 13:04 EDT

  None (edit)
Comment 20 errata-xmlrpc 2018-05-18 13:03:18 EDT
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-2018:1627

Note You need to log in before you can comment on or make changes to this bug.