Public bug reported: The LBaaS agent creates a lot of log messages, when a new lb-pool is created.
As soon as I create a lb-pool: neutron lb-pool-create --lb-method ROUND_ROBIN --name log-test-lb --protocol TCP --subnet-id a6ce9a77-53ca-4704-aaf4-fc255cc5fa74 The log file /var/log/neutron/neutron-lbaas-agent.log starts to fill up with messages like these: 2016-04-13 12:56:08.922 15373 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 37cbf817-f1ac-4d47-9a04-93c911d0afdd The message is correct, as the file /var/lib/neutron/lbaas/37cbf817 -f1ac-4d47-9a04-93c911d0afdd/sock is not present. But the message repeats every 10s. The messages stop as soon as the lb-pool gets a VIP. At this step the file /var/lib/neutron/lbaas/37cbf817-f1ac-4d47-9a04-93c911d0afdd/sock is present. I would expect the lbaas agent to verify the sock file could really be present before issuing the message. Version: Openstack Juno on SLES 11 SP3. The package version of openstack-neutron-lbaas-agent is 2014.2.2.dev26-0.11.2 ** Affects: neutron Importance: Undecided Status: New ** Tags: lbaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1569827 Title: LBaaS agent floods log when stats socket is not found Status in neutron: New Bug description: The LBaaS agent creates a lot of log messages, when a new lb-pool is created. As soon as I create a lb-pool: neutron lb-pool-create --lb-method ROUND_ROBIN --name log-test-lb --protocol TCP --subnet-id a6ce9a77-53ca-4704-aaf4-fc255cc5fa74 The log file /var/log/neutron/neutron-lbaas-agent.log starts to fill up with messages like these: 2016-04-13 12:56:08.922 15373 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 37cbf817-f1ac-4d47-9a04-93c911d0afdd The message is correct, as the file /var/lib/neutron/lbaas/37cbf817 -f1ac-4d47-9a04-93c911d0afdd/sock is not present. But the message repeats every 10s. The messages stop as soon as the lb-pool gets a VIP. At this step the file /var/lib/neutron/lbaas/37cbf817-f1ac-4d47-9a04-93c911d0afdd/sock is present. I would expect the lbaas agent to verify the sock file could really be present before issuing the message. Version: Openstack Juno on SLES 11 SP3. The package version of openstack-neutron-lbaas-agent is 2014.2.2.dev26-0.11.2 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1569827/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp