You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current code assumes that if a Node has been removed from the list on UpdateLoadBalancer(), we don't care about it's security group.
We could update applyNodeSecurityGroupIDForLB() to also lookup ports that have the SG tag and detach the SG from the ports that aren't belonging to the ports of the current list of Nodes.
@dulek hey there, you filed a bug some time ago about this issue and I'm taking over it. If time permits, let me know what you think about the proposed fix.
Current code assumes that if a Node has been removed from the list on
UpdateLoadBalancer()
, we don't care about it's security group.We could update
applyNodeSecurityGroupIDForLB()
to also lookup ports that have the SG tag and detach the SG from the ports that aren't belonging to the ports of the current list of Nodes.cloud-provider-openstack/pkg/openstack/loadbalancer_sg.go
Lines 72 to 99 in 04bd8e1
The text was updated successfully, but these errors were encountered: