yahoo-eng-team team mailing list archive

[haoliang <steven_lianghao@xxxxxxx>]

Public bug reported:

1.Under test tenement,create network:net1,subnet:subnet1,network address:192.168.1.0/24 and other keep default
2.Create router:R1,R1 inner interface relate to subnet1 and set outer network for R1
  Create VM1-1(port 80 is deny by iptables),choose subnet1,security group choose default,image is centos
  Create VM1-2(port 80 is deny by iptables),choose subnet1,security group choose default,image is centos
3.Create Resource Pool name "FZ1",choose subnet1,protocol is http,Load Blance Mode is ROUND_ROBIN
  Add VIP for"FZ1",set assign ip to 192.168.1.16,protocol port is 80 and other keep as default
4.Add member VM1-1 and VM1-2 for"FZ1",Weight is 1,protocol port is 80
5.Add "PING" monitor(delay is 1,timeout is 1,max retry times is 1)which is relate to FZ1
->the status of VM1-1 and VM1-2 is inactive should be active
6.stop iptables service in VM1-1 and VM1-2
->the status of VM1-1 and VM1-2 is active
In summary,"PING" monitor appear to work as "TCP" monitor

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  The "PING" monitor in load balance appear to work as "TCP" monitor

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  1.Under test tenement,create network:net1,subnet:subnet1,network address:192.168.1.0/24 and other keep default
  2.Create router:R1,R1 inner interface relate to subnet1 and set outer network for R1
    Create VM1-1(port 80 is deny by iptables),choose subnet1,security group choose default,image is centos
    Create VM1-2(port 80 is deny by iptables),choose subnet1,security group choose default,image is centos
  3.Create Resource Pool name "FZ1",choose subnet1,protocol is http,Load Blance Mode is ROUND_ROBIN
    Add VIP for"FZ1",set assign ip to 192.168.1.16,protocol port is 80 and other keep as default
  4.Add member VM1-1 and VM1-2 for"FZ1",Weight is 1,protocol port is 80
  5.Add "PING" monitor(delay is 1,timeout is 1,max retry times is 1)which is relate to FZ1
  ->the status of VM1-1 and VM1-2 is inactive should be active
  6.stop iptables service in VM1-1 and VM1-2
  ->the status of VM1-1 and VM1-2 is active
  In summary,"PING" monitor appear to work as "TCP" monitor

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