yahoo-eng-team team mailing list archive

[berlin <linb@xxxxxxxxxx>]

Public bug reported:

I remember some one else reported the bug, but i didn't search it and
not sure whether it is the same reason. So i report the bug here again.

After deploying a LBaaS service(vip&pool&member&monitor) with haproxy,
then set the admin_state_up of VIP|POLL to False, the haproxy still
works and you can still use the LBaaS service.

Root reason:  Although the haproxy agent adds check when creating a
loadbalancer service and if the admin_state_up is false, the haproxy
would not create the haproxy process. But the haproxy agent did not
consider setting admin_state_up to False for a lbaas services whose
process is  in running state.

** 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/1302333

Title:
  LBaaS haproxy process still wok after setting admin_state_up of
  VIP|POOL to False

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I remember some one else reported the bug, but i didn't search it and
  not sure whether it is the same reason. So i report the bug here
  again.

  After deploying a LBaaS service(vip&pool&member&monitor) with haproxy,
  then set the admin_state_up of VIP|POLL to False, the haproxy still
  works and you can still use the LBaaS service.

  Root reason:  Although the haproxy agent adds check when creating a
  loadbalancer service and if the admin_state_up is false, the haproxy
  would not create the haproxy process. But the haproxy agent did not
  consider setting admin_state_up to False for a lbaas services whose
  process is  in running state.

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