[Bug 1738122] Re: lbaas haproxy "backend has no server available" spamming terminal via systemd

[James Page]

** Also affects: neutron (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: charm-neutron-gateway
       Status: New => Invalid

** Changed in: charm-neutron-api
       Status: New => Invalid

** Changed in: neutron (Ubuntu)
       Status: New => Triaged

** Changed in: neutron (Ubuntu)
   Importance: Undecided => Low

** Package changed: neutron (Ubuntu) => neutron-lbaas (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1738122

Title:
  lbaas haproxy "backend has no server available" spamming terminal via
  systemd

Status in OpenStack neutron-api charm:
  Invalid
Status in OpenStack neutron-gateway charm:
  Invalid
Status in neutron-lbaas package in Ubuntu:
  Triaged

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 at cmg01z00infr001:~$ juju config neutron-gateway debug
  true
  jujumanage at cmg01z00infr001:~$ juju config neutron-gateway verbose
  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://pastebin.ubuntu.com/26180641/ for details of related
  processes running and messages from systemd-journald.

  
  Running on xenial
  python-neutron-lbaas                 2:10.0.1-0ubuntu1~cloud0
  haproxy                              1.6.3-1ubuntu0.1

  17.08 charms

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-api/+bug/1738122/+subscriptions