← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1622946] [NEW] lbaas with haproxy backend creates the lbaas namespace without the members' subnet

 

Public bug reported:

When creating a new loadbalancer with haproxy, and the VIP and member
subnets are different, the created lbaas namespace contains only the VIP
subnet, so the members are unreachable.

E.g.:
neutron lbaas-loadbalancer-show 8e1c193a-ab63-4a1a-bc39-c663f2f9a0ee
.
.
.
| vip_subnet_id       | 23655977-d29f-4917-a519-de27951fde89           |

neutron lbaas-member-list d3ebda43-53f8-4118-b4db-999c021c9680

| 4fe79d5e-a517-4e4f-a145-3c80b414be08 |      | 192.168.168.8 |
22 |      1 | 0a4a1f3e-43cb-4f9c-9d51-c71f0c231a3e | True           |

Note that the two subnets are different.
The created haproxy config is OK:
.
.
.
frontend 6821edd8-54ab-4fba-90e5-94831fcd0ec0
    option tcplog
    bind 10.97.37.1:22
    mode tcp

backend d3ebda43-53f8-4118-b4db-999c021c9680
    mode tcp
    balance source
    timeout check 20
    server 4fe79d5e-a517-4e4f-a145-3c80b414be08 192.168.168.8:22 weight 1 check inter 10s fall 3

But the namespace is not:
ip netns exec qlbaas-8e1c193a-ab63-4a1a-bc39-c663f2f9a0ee ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ns-f56b5f8d-ef@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether fa:16:3e:82:9d:9a brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.97.37.1/25 brd 10.97.37.127 scope global ns-f56b5f8d-ef
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe82:9d9a/64 scope link 
       valid_lft forever preferred_lft forever


The member subnet is missing.

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

Title:
  lbaas with haproxy backend creates the lbaas namespace without the
  members' subnet

Status in neutron:
  New

Bug description:
  When creating a new loadbalancer with haproxy, and the VIP and member
  subnets are different, the created lbaas namespace contains only the
  VIP subnet, so the members are unreachable.

  E.g.:
  neutron lbaas-loadbalancer-show 8e1c193a-ab63-4a1a-bc39-c663f2f9a0ee
  .
  .
  .
  | vip_subnet_id       | 23655977-d29f-4917-a519-de27951fde89           |

  neutron lbaas-member-list d3ebda43-53f8-4118-b4db-999c021c9680

  | 4fe79d5e-a517-4e4f-a145-3c80b414be08 |      | 192.168.168.8 |
  22 |      1 | 0a4a1f3e-43cb-4f9c-9d51-c71f0c231a3e | True           |

  Note that the two subnets are different.
  The created haproxy config is OK:
  .
  .
  .
  frontend 6821edd8-54ab-4fba-90e5-94831fcd0ec0
      option tcplog
      bind 10.97.37.1:22
      mode tcp

  backend d3ebda43-53f8-4118-b4db-999c021c9680
      mode tcp
      balance source
      timeout check 20
      server 4fe79d5e-a517-4e4f-a145-3c80b414be08 192.168.168.8:22 weight 1 check inter 10s fall 3

  But the namespace is not:
  ip netns exec qlbaas-8e1c193a-ab63-4a1a-bc39-c663f2f9a0ee ip addr
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever
  2: ns-f56b5f8d-ef@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether fa:16:3e:82:9d:9a brd ff:ff:ff:ff:ff:ff link-netnsid 0
      inet 10.97.37.1/25 brd 10.97.37.127 scope global ns-f56b5f8d-ef
         valid_lft forever preferred_lft forever
      inet6 fe80::f816:3eff:fe82:9d9a/64 scope link 
         valid_lft forever preferred_lft forever

  
  The member subnet is missing.

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


Follow ups