yahoo-eng-team team mailing list archive

[Eran Kuris <ekuris@xxxxxxxxxx>]

Public bug reported:

I created in LBaaS  2  VIP's .
I  associate one vip (192.168.1.8) to external IP  (10.35.166.4).
When I try to associate the second vip(192.168.1.9) to same external IP 10.35.166.4  I success but it overwrite the first vip  , there is no warning message. 
We should prevent it as we cannot associate VM to external IP that already associated to other VM (we get an error message : Conflict (HTTP 409) (Request-ID: req-35eeddc9-d264-4fc5-a336-d201e4a66231 ])

**If we not prevent it we should send warning message about it .


How to Reproduce : 
Create in your tenant 2 VM's  with internal network & external network.

1. Create LB pool on subnet of tenant A
<neutron  lb-pool-create  --lb-method ROUND_ROBIN --name webpool --protocol HTTP --subnet-id <subnet-id>>

2. Log into VM1 and VM2, enable httpd
<service httpd restart>

3. Create 2 members into webpool (use VM’s Ips)
<neutron  lb-member-create --address  <IP> --protocol-port 80 webpool>

4.Create a Healthmonitor and associated it with the webpool

<neutron lb-healthmonitor-create --delay 3 --type HTTP --max-retries 3
--timeout 3>

Run:
<neutron lb-healthmonitor-list>

<neutron lb-healthmonitor-associate <healthmonitor-id> webpool

5.Create a VIP for the webpool
<neutron lb-vip-create --name webvip --protocol-port 80 --protocol HTTP --subnet-id <subnet-id> webpool>

6.Check HAproxy created (for example)
<ps -ef | grep haproxy>

7. Create a floating IP from external network
<neutron floatingip-create <external network name>

8.Check port id of LB VIP
<neutron port-list>
<neutron floatingip-list>

9.Associate floating IP with the LB VIP
<neutron floatingip-associate <floatingip-id> <port-id of LB VIP>

10.From external network, try to connect the floating IP by curl 
<curl http://IP>


create for same VM's  VIP  to other service FTP  or SSH  for example  and try to associate it to same external floating ip that we used already.

** Affects: neutron
     Importance: Undecided
         Status: New

** Attachment added: "LBaaS floating IP .odt"
   https://bugs.launchpad.net/bugs/1421239/+attachment/4317992/+files/LBaaS%20floating%20IP%20.odt

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

Title:
  LBaaS- overwrite when associate  2 different Vip's  to same external
  IP

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I created in LBaaS  2  VIP's .
  I  associate one vip (192.168.1.8) to external IP  (10.35.166.4).
  When I try to associate the second vip(192.168.1.9) to same external IP 10.35.166.4  I success but it overwrite the first vip  , there is no warning message. 
  We should prevent it as we cannot associate VM to external IP that already associated to other VM (we get an error message : Conflict (HTTP 409) (Request-ID: req-35eeddc9-d264-4fc5-a336-d201e4a66231 ])

  **If we not prevent it we should send warning message about it .


  How to Reproduce : 
  Create in your tenant 2 VM's  with internal network & external network.

  1. Create LB pool on subnet of tenant A
  <neutron  lb-pool-create  --lb-method ROUND_ROBIN --name webpool --protocol HTTP --subnet-id <subnet-id>>

  2. Log into VM1 and VM2, enable httpd
  <service httpd restart>

  3. Create 2 members into webpool (use VM’s Ips)
  <neutron  lb-member-create --address  <IP> --protocol-port 80 webpool>

  4.Create a Healthmonitor and associated it with the webpool

  <neutron lb-healthmonitor-create --delay 3 --type HTTP --max-retries 3
  --timeout 3>

  Run:
  <neutron lb-healthmonitor-list>

  <neutron lb-healthmonitor-associate <healthmonitor-id> webpool

  5.Create a VIP for the webpool
  <neutron lb-vip-create --name webvip --protocol-port 80 --protocol HTTP --subnet-id <subnet-id> webpool>

  6.Check HAproxy created (for example)
  <ps -ef | grep haproxy>

  7. Create a floating IP from external network
  <neutron floatingip-create <external network name>

  8.Check port id of LB VIP
  <neutron port-list>
  <neutron floatingip-list>

  9.Associate floating IP with the LB VIP
  <neutron floatingip-associate <floatingip-id> <port-id of LB VIP>

  10.From external network, try to connect the floating IP by curl 
  <curl http://IP>

  
  create for same VM's  VIP  to other service FTP  or SSH  for example  and try to associate it to same external floating ip that we used already.

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