yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

health monitor is a shared object, so when you disassociate it from the
pool, it us undeployed from particular backend, but the health monitor
as a shared entity remains in the DB (it actually could be associated
with several pools simultaneously)

So you're observing expected behavior

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1336174

Title:
  lbaas-agent: healthmonitor disassociate invokes delete

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Hello,

  I am adding a LBaaS driver, and in that I see that

      neutron lb-healthmonitor-disassociate <hmon-id> <pool-id>

  invokes `delete_pool_health_monitor` function in the driver!, but the 
  monitor is *not* actually removed from the DB
  and 

      neutron lb-healthmonitor-delete <hmon-id>

  will do the cleanup

  Is this expected ? I expected the `disassociate` option to call
  `update_pool_health_monitor` in the driver.

  (I am on Icehouse, RDO)

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