Bug 1327931
Summary: | LBaasV2 pool creation with session persistence [HTTP_COOKIE] is getting failed | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | VIKRANT <vaggarwa> |
Component: | openstack-neutron-lbaas | Assignee: | Nir Magnezi <nmagnezi> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Stafeyev <astafeye> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | amuller, apevec, astafeye, lhh, lpeer, nyechiel, oblaut, tfreger, vaggarwa |
Target Milestone: | async | Keywords: | ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-neutron-lbaas-2015.1.2-2.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Neutron LBaaS v2 was using the 'session_persistence' and 'sessionpersistence' strings inconsistently throughout the neutron-server and LBaaS v2 agent, resulting in the creation of a load balancing pool to return success, meanwhile the agent was raising an exception and failing to configure haproxy.
Consequence:
The inability to create a load balancing pool with session persistence defined.
Fix:
Eliminate the source of the exception by using the 'session_persistence' and 'sessionpersistence' strings consistently.
Result:
The session persistency may now be used when creating a load balancing pool via the LBaaS v2 API.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-24 14:54:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
VIKRANT
2016-04-18 03:58:09 UTC
Tested it on my environment (KILO AIO setup - packstack installation) persistence works well. Can see the Set-Cookie in the first response, the cookie in the following requests. The requests go only to 1 member ( configured 2 ) BR openstack-neutron-lbaas-2015.1.2-2.el7ost.noarch.rpm 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://rhn.redhat.com/errata/RHBA-2016-1103.html |