haproxy configuration spams logged-in users when no servers are available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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@
haproxy[
Message from syslogd@
haproxy[
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.
Changed in neutron: | |
assignee: | nobody → John Schwarz (jschwarz) |
status: | New → In Progress |
description: | updated |
description: | updated |
Changed in neutron: | |
assignee: | John Schwarz (jschwarz) → nobody |
Changed in neutron: | |
status: | In Progress → Fix Released |
This sounds like a good idea and should be done in the V2 config and namespace driver.