Bug 1303030

Summary:	[RFE] get haproxy stats from the local IPs on the instances
Product:	Red Hat OpenStack	Reporter:	David Juran <djuran>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	bfournie, bperkins, derekh, djuran, dsneddon, dtantsur, jcoufal, kbasil, lmiccini, mburns, mcornea, oblaut, rhel-osp-director-maint
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-12 08:41:20 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:

Description David Juran 2016-01-29 11:08:23 UTC

Description of problem:
I've found that when deploying an HA overcloud with network isolation, the haproxy stats ends up listening to a VIP.
I.e. the following snippet from /etc/haproxy/haproxy.cfg

listen haproxy.stats
  bind 192.0.2.19:1993 
  mode http
  stats enable
  stats uri /

Now do note that 192.0.2.19 is a VIP. Which means the stats from the other two haproxy instances, which may be handling e.g. the public or private API:s are not accessable.

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.6-94.el7ost



Expected results:
I would expect the haproxy stats to be listening on a local IP on each instance.

Additional info:
Do note that with the default configuration, the haproxy stats end up on the provisioning network. Not quite convinced this is the intuitive choice...

Comment 2 Mike Burns 2016-04-07 21:07:13 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 5 David Juran 2016-10-20 15:52:20 UTC

This is still happening with OSP9, the haproxy.stats service is listening to a VIP

Comment 6 Bob Fournier 2016-10-31 18:52:46 UTC

From puppet-tripleo/manifests/haproxy.pp, this is where it is added:

   $haproxy_stats_bind_opts = {
      "${controller_virtual_ip}:1993" => $haproxy_listen_bind_param,

This seems to be logical IP to use to count packets haproxy stats, but following up
on this.

Comment 7 Bob Fournier 2016-11-01 19:53:27 UTC

Yes, using the controller VIP is the implemented and expected IP to use for haproxy stats.  The recommendation is to close this as NOTABUG and open an separate RFE to get stats from the local IPs on the instances.

Comment 8 Dmitry Tantsur 2016-11-02 09:26:40 UTC

Thanks Bob! Converting to an RFE and stopping targeting Newton. Please check if the updated title is right.

Comment 15 Luca Miccini 2020-02-12 08:41:20 UTC

as far as I can see it is fixed in both osp13 and osp16, I hope it is OK for you/your customer.