Closed jgruber closed 7 years ago
Escalating to Bug-Serverity-1-Critical ... Customer impacting now.
The loadbalancer (listener is where the traffic group is set) does not apply the traffic group for the tenant, but the SNAT translation address does. This means that when failover is tested all connections using SNAT (which is all of them) are reset rather then failing to the next peer in the DSG.
Have a fix for this. Peer reviewed with Jeff. Will push later today once I have implemented a test for it.
Thanks all
It would be great if you could produce .debs. I would test if the issue is still reproducible. I'm going to be on PTO a couple of days. I will be back this Tuesday 27th EMEA time zone.
Please also include the fixes of https://github.com/F5Networks/f5-openstack-agent/issues/304
John,
I have a deb for you to try. I don't know if you are already on vacation, but this was a fast as I could get to it.
Regards,
Rich
On Thu, Sep 22, 2016 at 4:08 AM, alonsocamaro notifications@github.com wrote:
Thanks all
It would be great if you could produce .debs. I would test if the issue is still reproducible. I'm going to be on PTO a couple of days. I will be back this Tuesday 27th EMEA time zone.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/F5Networks/f5-openstack-agent/issues/321#issuecomment-248861179, or mute the thread https://github.com/notifications/unsubscribe-auth/AIVe0ZOXVDGR9xldqwLMr5Pxl3GXOpryks5qslOYgaJpZM4KCIv3 .
Hi Rich
I would like to try the that .deb file. Please also include https://github.com/F5Networks/f5-openstack-agent/issues/304
Thanks
Ulises
Title: LBaaS agent in scalen mode does properly populate the traffic_group for listeners
Details: When the agent starts it collects all provisioned traffic groups on the BIG-IP, removing only the local_only traffic group. When a load_balancer is requested the traffic_group is intended to be populated from a the collected traffic_group list with tenant affinity. The traffic_group for the virtual_address is always /Common/traffic-group-1 always.
OpenStack Release
Mitaka
Description
It appears that the traffic_group is selected, but when passed to lbaas_builder.assure_service as a kwarg, nothing is done with it. When the listener_service attempts to get the traffic_group as an attribute of the loadbalancer service object. That attribute is not populate.
Agent Version
9.0.3
Operating System
RHOS on CentOS7
Deployment
LBaaS agent provisioned with 'scalen' mode configured to provision a three or more member sync-failover DSG. The devices should have at least 6 traffic groups configured with the traffic-group-1 removed or else renamed to see the behavior.