yahoo-eng-team team mailing list archive

[Alan Pevec <1398754@xxxxxxxxxxxxxxxxxx>]

** Changed in: horizon/kilo
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1398754

Title:
  LBaas v1 Associate Monitor to Pool Fails

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Dashboard (Horizon) kilo series:
  Fix Released

Bug description:
  Try to associate health monitor to pool in horizon, there's no monitor
  listed on page "Associate Monitor".

  Reproduce Procedure: 
  1.  Create Pool 
  2.  Add two members
  3.  Create Health Monitor
  4.  Click "Associate Monitor" button of pool resource
  5.  There's no monitor listed.

  ***************************
  At this point, use CLI to:
  1.  show pool, there's no monitor associated yet.
  +------------------------+--------------------------------------+
  | Field                      | Value                                      |
  +------------------------+--------------------------------------+
  | health_monitors        |                                         |
  | health_monitors_status |                                  |
  +------------------------+--------------------------------------+

  2. list monitor, there's available monitor.
  $ neutron lb-healthmonitor-list
  +--------------------------------------+------+----------------+
  | id                                   | type | admin_state_up |
  +--------------------------------------+------+----------------+
  | f5e764f0-eceb-4516-9919-7806f409c1ae | HTTP | True           |
  +--------------------------------------+------+----------------+

  3. Assocaite monitor to pool. Succeeded.
  $ neutron lb-healthmonitor-associate  f5e764f0-eceb-4516-9919-7806f409c1ae  mypool
  Associated health monitor f5e764f0-eceb-4516-9919-7806f409c1ae

  *************************************************

  Base on above info, it should be a horizon bug. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1398754/+subscriptions