yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95933
[Bug 2112110] [NEW] [ovn-octavia-provider] LoadBalancer member not coming back after disable-enable
Public bug reported:
The logical over the disable/enable for a member looks not working fine
if a HM is checking the pool where member is attached. If you disable a
backend member and put it enable again it is not comming as a available
backend member to redirect LB traffic:
Step to reproduce the issue.
1. Create a Load Balancer with:
A listener on port 80 using TCP protocol
A pool with a HM attached
2. Add a VM (which is Active) to the pool as a member:
The load balancer works correctly
HM reports correctly the status as ONLINE
3. Disable the member
HM reports the status as ERROR, where OFFLINE looks more appropiate
4. Enable the member
HM doesn't detect the change and mantain the ERROR status not checking again the probes to the member so movin to ONLINE, also vips field keeps {} (empty)
** Affects: neutron
Importance: Undecided
Assignee: Fernando Royo (froyoredhat)
Status: New
** Tags: ovn-octavia-provider
** Changed in: neutron
Assignee: (unassigned) => Fernando Royo (froyoredhat)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2112110
Title:
[ovn-octavia-provider] LoadBalancer member not coming back after
disable-enable
Status in neutron:
New
Bug description:
The logical over the disable/enable for a member looks not working
fine if a HM is checking the pool where member is attached. If you
disable a backend member and put it enable again it is not comming as
a available backend member to redirect LB traffic:
Step to reproduce the issue.
1. Create a Load Balancer with:
A listener on port 80 using TCP protocol
A pool with a HM attached
2. Add a VM (which is Active) to the pool as a member:
The load balancer works correctly
HM reports correctly the status as ONLINE
3. Disable the member
HM reports the status as ERROR, where OFFLINE looks more appropiate
4. Enable the member
HM doesn't detect the change and mantain the ERROR status not checking again the probes to the member so movin to ONLINE, also vips field keeps {} (empty)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2112110/+subscriptions