haproxy configuration spams logged-in users when no servers are available

[John Schwarz]

On certain systems which use the default syslog configuration, using haproxy-based LBaaS causes error logs to spam all the logged-in users:

Message from syslogd@alpha-controller at Jun 9 01:32:07 ...
 haproxy[2719]:backend 32fce5ee-b7f7-4415-a572-a83eba1be6b0 has no server available!

Message from syslogd@alpha-controller at Jun 9 01:32:07 ...
 haproxy[2719]:backend 32fce5ee-b7f7-4415-a572-a83eba1be6b0 has no server available!

The error message is valid - it happens when, for example, there are no backend servers available to handle the service requests because all members are down.
However, there is no point in sending the messages to all the logged-in users. The wanted result is that each namespace will have its own log file, which will contain all the log messages that the relevant haproxy process produces. This log file should be placed in the $state_path/lbaas path along with the other files (conf, pid...), to be later accessed by the setup's administrator.

[Brandon Logan (brandon-logan)]

This sounds like a good idea and should be done in the V2 config and namespace driver.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/119731

[OpenStack Infra (hudson-openstack)]

Change abandoned by Salvatore Orlando (<email address hidden>) on branch: master
Review: https://review.openstack.org/119731
Reason: This patch has been inactive long enough that I think it's safe to abandon.
The author can resurrect it if needed.

[Pavel Fedin (p-fedin)]

 Hello!
 I am currently having this issue with recent DevStack on CentOS 7. Therefore, it's still relevant.

[Appasaheb Sawant (appasaheb-sawant)]

Is this fixed on your side? I am facing same issue.

[Appasaheb Sawant (appasaheb-sawant)]

I am facing same issue. Please let me if anybody fixed it

Broadcast message from systemd-journald@XXXXX (Tue 2016-09-13 09:18:41 PDT):

haproxy[13631]: backend 247f3449-993a-43d5-9d43-78c439892099 has no server available!

Broadcast message from systemd-journald@XXXXX (Tue 2016-09-13 09:18:41 PDT):

haproxy[13631]: backend 247f3449-993a-43d5-9d43-78c439892099 has no server available!

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron-lbaas 13.0.0.0b1 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron-lbaas 11.0.4 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron-lbaas queens-eol release.