neutron-lbaasv2-agent using haproxy backend spams console via systemd-journald when lbaas has no backends
Bug #1831096 reported by
Drew Freiberger
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Neutron Gateway Charm |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When running LBAAS v2 on xenial-queens neutron-gateway units, if the backends for a given lbaas are unavailable, we get console/user session spam from systemd-journald like:
Broadcast message from systemd-
haproxy[1557767]: backend 2363f66f-
Broadcast message from systemd-
haproxy[1557767]: backend 2363f66f-
This should be suppressed to only show up in haproxy.log or syslog, but not sent to all logged in users, as this is an overcloud warning, not an issue with the undercloud.
| Changed in charm-neutron-gateway: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
