Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1581337 - Add config for disabling creation of PING type HMs
Add config for disabling creation of PING type HMs
Status: ON_DEV
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
high Severity high
: ---
: 13.0 (Queens)
Assigned To: Nir Magnezi
Alexander Stafeyev
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-22 10:28 EDT by Nir Magnezi
Modified: 2018-07-26 12:24 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
In order to use the PING type health monitor, the HAProxy (default software we use in our driver for network load balancing) version must be at least 1.6. Any use of an older HAProxy version makes the health-check be TCP connect without the user's knowledge. The upstream community fixed that by adding a check in the code, that determine the HAProxy version that is in use and acts accordingly: If HAProxy version 1.6 or later, we can use PING. Otherwise, we keep using TCP connect (in the absence of any other solution for those haproxy versions, it is better to do so rather than breaking it altogether). The problem we have in OSP13 GA is that we ship HAProxy as a part of RHEL channels, which uses an old version of HAProxy. Thus, when OSP13 users configure the PING type health monitor, they will get TCP connect instead.
Story Points: ---
Clone Of:
Environment:
Last Closed:
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)

  None (edit)
Description Nir Magnezi 2018-05-22 10:28:54 EDT
Description of problem:
=======================
In OSP13, we ship an old version of haproxy who does not support external monitors. Thus, ping type health monitors does not actually work (it uses tcp connect instead).

We should block ping type HMs by default and produce a warning to the user.

Most of this is covered by: https://review.openstack.org/#/c/528439/

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