Lbaas driver could pick the wrong member address in dual stack network
Bug #1813089 reported by
Hang Yang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
senlin |
Fix Released
|
Undecided
|
Hang Yang |
Bug Description
Currently when Senlin adds a member to a load balancer's pool, it just uses the first address of the node.[1] In a dual stack network, if the node's first address does not match with the ip_version of the pool's subnet, the member will become unaccessible from the load balancer.
[1] https:/
Changed in senlin: | |
assignee: | nobody → Hang Yang (hangyang) |
Changed in senlin: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/632830 /git.openstack. org/cgit/ openstack/ senlin/ commit/ ?id=ec3c42a2ad0 644b0b342cbebb5 0820eafb7d916e
Committed: https:/
Submitter: Zuul
Branch: master
commit ec3c42a2ad0644b 0b342cbebb50820 eafb7d916e
Author: Hang Yang <email address hidden>
Date: Wed Jan 23 15:25:12 2019 -0800
Fix member address selection in lbaas driver
Currently when Senlin adds a member to load balancer's pool, it just uses
the first address of the node. In a dual stack network, if the first
address does not match with the subnet ip version, the member will become
unaccessible from the load balancer. This patch ensures the right address
will be picked according to the subnet ip version.
Change-Id: I0322184dfdb46a 7560c20e85452d8 4d2ffb83a1c
Closes-Bug: #1813089