Bug 1196249

Summary: LBaaS health monitor created from horizon shows associated with all pools
Product: Red Hat OpenStack Reporter: Sadique Puthen <sputhenp>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0 (Juno)CC: amedeo.salvati, aortega, athomas, dmaley, mrunge, nbaechtold, nyechiel, oblaut, pablo.iranzo, pmukhedk, sputhenp, tfreger, yeylon
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-2014.2.3-4.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-24 20:16:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Pool_view
none
HM_view none

Description Sadique Puthen 2015-02-25 15:06:50 UTC 
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.
Comment 4 Matthias Runge 2015-02-25 19:50:17 UTC 
No need to put in a needinfo without a specific question. I'm monitoring bz very closely.
Comment 8 Matthias Runge 2015-06-09 14:03:43 UTC 
https://review.openstack.org/189728
Comment 20 Alexander Stafeyev 2015-08-16 13:22:40 UTC 
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
Comment 21 Alexander Stafeyev 2015-08-17 07:30:00 UTC 
Created attachment 1063661 [details]
Pool_view
Comment 22 Alexander Stafeyev 2015-08-17 07:30:40 UTC 
Created attachment 1063662 [details]
HM_view
Comment 23 Alexander Stafeyev 2015-08-17 07:32:44 UTC 
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
Comment 24 Alexander Stafeyev 2015-08-18 14:11:05 UTC 
Pls IGNORE comment 20 

tnx
Comment 26 errata-xmlrpc 2015-08-24 20:16:02 UTC 
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
Comment 28 Red Hat Bugzilla 2023-09-18 00:11:14 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days