← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #49367

[Bug 1421239] Re: LBaaS- overwrite when associate 2 different Vip's to same external IP

  Thread Previous • Date Previous • • Thread Next 
** Changed in: neutron
       Status: Incomplete => Invalid

** Changed in: neutron
       Status: Invalid => 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/1421239

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

Status in neutron:
  New

Bug description:
  Version :
  [root@puma15 ~]# rpm -qa |grep neutron
  openstack-neutron-openvswitch-2014.2.1-6.el7ost.noarch
  python-neutronclient-2.3.9-1.el7ost.noarch
  openstack-neutron-2014.2.1-6.el7ost.noarch
  python-neutron-2014.2.1-6.el7ost.noarch
  openstack-neutron-ml2-2014.2.1-6.el7ost.noarch

  
  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.

  see the command I entered :
  __________________________________________________

  [root@puma15 ~(keystone_eran1)]# neutron port-list
  +--------------------------------------+------------------------------------------+-------------------+-------------------------------------------------------------------------------------+
  | id                                   | name                                     | mac_address       | fixed_ips                                                                           |
  +--------------------------------------+------------------------------------------+-------------------+-------------------------------------------------------------------------------------+
  | 17552712-9b66-466b-8836-7e09a15f439a |                                          | fa:16:3e:6d:93:c3 | {"subnet_id": "cff1967c-dd18-4247-849d-97c363c39b4f", "ip_address": "10.35.166.5"}  |
  | 2668a4e8-7ddf-4242-813b-5febe7269d1b |                                          | fa:16:3e:9d:d0:cd | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.3"}  |
  | 3f9691df-9e33-4ea2-812a-83d51fdf45a1 |                                          | fa:16:3e:12:18:fb | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.6"}  |
  | 4004c3d0-390a-4db6-9c2c-b96b4a920af8 |                                          | fa:16:3e:df:08:6f | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.1"}  |
  | 460dafb7-3d05-4494-a83d-416b82b4eace | vip-adc9c688-97d2-425b-abd0-29505ac10a76 | fa:16:3e:65:8d:ff | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.56"} |
  | 6eba1c27-d202-470b-b89b-73a569d9da00 |                                          | fa:16:3e:4d:b9:18 | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.7"}  |
  | 73149116-32e8-4960-a0a5-286bdb117d96 | vip-bc9c9025-db2c-40cd-8663-50c687639ff1 | fa:16:3e:75:53:33 | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.55"} |
  | 8f6ba5ab-12d8-4b1c-b78f-60bf90210dc9 |                                          | fa:16:3e:ee:a7:a3 | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", "ip_address": "192.168.2.4"}  |
  | aad2870a-4f18-4471-985f-943911dfaaf3 |                                          | fa:16:3e:d9:d7:85 | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", "ip_address": "192.168.2.3"}  |
  | b359ba1f-dde1-4576-9904-644acb032c4f |                                          | fa:16:3e:92:d9:8c | {"subnet_id": "cff1967c-dd18-4247-849d-97c363c39b4f", "ip_address": "10.35.166.4"}  |
  | b471ddb4-d1b8-4df0-b098-60a2a45a1d4f |                                          | fa:16:3e:8c:5b:4c | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", "ip_address": "192.168.2.1"}  |
  | c0fe10e3-32b8-4373-b848-8d9ba5879a41 |                                          | fa:16:3e:f8:df:23 | {"subnet_id": "cff1967c-dd18-4247-849d-97c363c39b4f", "ip_address": "10.35.166.1"}  |
  | e0d22e23-a2be-4417-97cd-cadd7bb91d8f |                                          | fa:16:3e:cf:aa:81 | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", "ip_address": "192.168.2.2"}  |
  +--------------------------------------+------------------------------------------+-------------------+-------------------------------------------------------------------------------------+
  [root@puma15 ~(keystone_eran1)]# neutron floatingip-list
  +--------------------------------------+------------------+---------------------+--------------------------------------+
  | id                                   | fixed_ip_address | floating_ip_address | port_id                              |
  +--------------------------------------+------------------+---------------------+--------------------------------------+
  | 068feb10-4336-443d-8369-3e9e0913f362 | 192.168.1.55     | 10.35.166.4         | 73149116-32e8-4960-a0a5-286bdb117d96 |
  | a63c323c-3aeb-46a8-b6e5-97c02aa85e3a |                  | 10.35.166.5         |                                      |
  +--------------------------------------+------------------+---------------------+--------------------------------------+

  [root@puma15 ~(keystone_eran1)]# neutron floatingip-associate  068feb10-4336-443d-8369-3e9e0913f362 460dafb7-3d05-4494-a83d-416b82b4eace
  Associated floating IP 068feb10-4336-443d-8369-3e9e0913f362
  [root@puma15 ~(keystone_eran1)]#

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

References

  Thread Previous • Date Previous • • Thread Next