Red Hat Bugzilla – Bug 1196249
LBaaS health monitor created from horizon shows associated with all pools
Last modified: 2016-09-15 07:48:47 EDT
Description of problem: There appears to be a dashboard bug that displays monitors incorrectly which leads to us not being able to associate them. We are able to create a load balancer monitor, but whenever we do, they immediately show up as associated to every pool in every tenant. This is a display problem, because when we check this at the command line and also in the database, they are not in fact associated. We can not use the dashboard UI to actually associate them, because it thinks it is already associated with all available checks when it really is not. When I associate a pool and monitor at the command line then the monitor is correctly hooked up. At that point the dashboard DOES show the correct attachment information on the pool, and the pool no longer shows up on the wrong monitors. Version-Release number of selected component (if applicable): OSP6 GA. How reproducible: Always. Steps to Reproduce: 1. Create some lbaas pools from dashboard. 2. Create monitors dashboard. 3. The monitor shows associated with all the pools before we associate it with them. Actual results: The monitor shows associated with all the pools before we associate it with them. Expected results: The monitor should be shown as not associated with any pools till we associate them. Additional info: Attaching screenshots and cli output to show it's not associated in back end or db, but it's a minor GUI glitch.
No need to put in a needinfo without a specific question. I'm monitoring bz very closely.
https://review.openstack.org/189728
Tried to reproduce. After creating Pools I tried to create HM but this action failed . These are the messages we see in lbaas log. the IDs are pool IDs. 2015-08-16 16:19:21.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 10bd5190-d8a2-48fc-bfdc-0d64201e221b 2015-08-16 16:19:21.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 3bdc2bca-abb5-4b08-b10b-4725ba489f52 2015-08-16 16:19:21.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool b1fe3671-88d5-454a-b1f8-801e80fb1171 2015-08-16 16:19:31.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 10bd5190-d8a2-48fc-bfdc-0d64201e221b 2015-08-16 16:19:31.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 3bdc2bca-abb5-4b08-b10b-4725ba489f52 2015-08-16 16:19:31.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool b1fe3671-88d5-454a-b1f8-801e80fb1171 2015-08-16 16:19:41.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 10bd5190-d8a2-48fc-bfdc-0d64201e221b 2015-08-16 16:19:41.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 3bdc2bca-abb5-4b08-b10b-4725ba489f52 2015-08-16 16:19:41.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool b1fe3671-88d5-454a-b1f8-801e80fb1171 2015-08-16 16:19:51.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 10bd5190-d8a2-48fc-bfdc-0d64201e221b 2015-08-16 16:19:51.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool 3bdc2bca-abb5-4b08-b10b-4725ba489f52 2015-08-16 16:19:51.726 16858 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Stats socket not found for pool b1fe3671-88d5-454a-b1f8-801e80fb1171
Created attachment 1063661 [details] Pool_view
Created attachment 1063662 [details] HM_view
Whe we look from pool view it seems that no HM are associated to the pool BUT when we look from HM view it shows that the HM is associated with all the pools attachments are added
Pls IGNORE comment 20 tnx
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1679.html