lbaas haproxy "backend has no server available" spamming terminal via systemd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron API Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Neutron Gateway Charm |
Invalid
|
Undecided
|
Unassigned | ||
neutron-lbaas (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
We are finding the haproxy for lbaas agents that are in a state of not having instances related to them on the backend are spamming user ssh terminals.
This should be sufficient to be in haproxy logs. It makes it very difficult to work on the units.
Settings in n-gw charm are
jujumanage@
true
jujumanage@
false
I wonder if debug is sending to STDERR as well as the log. Even so, I'd rather systemd be configured to not forward that on to terminals.
Please see http://
Running on xenial
python-
haproxy 1.6.3-1ubuntu0.1
17.08 charms
Changed in charm-neutron-gateway: | |
status: | New → Invalid |
Changed in charm-neutron-api: | |
status: | New → Invalid |
Changed in neutron (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
affects: | neutron (Ubuntu) → neutron-lbaas (Ubuntu) |