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
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
While testing shared loadbalancers, i think i discovered a regression since this PR.
A shared loadbalancer is renamed due to this if. What happens here is :
We enter the ensureOctaviaLoadBalancer function as clusterb with a shared loadbalancer named : kube_service_clustera_kns_fakeservice
At the end we can see the cluster has been renamed : kube_service_clusterb_kns_fakeservice.
And we have the event : Warning LoadBalancerRename Loadbalancer fakeloadbalancerid has a name of kube_service_clustera_kns_fakeservice with incorrect cluster-name component. Renaming it to kube_service_clusterb_kns_fakeservice.
The tags has been changed too : ["kube_service_clustera_kns_fakeservice","clustera","kube_service_clusterb_kns_fakeservice"]
become ["kube_service_clusterb_kns_fakeservice","clustera","kube_service_clusterb_kns_fakeservice"]
Didn't test if it's the case , but i suspect that if we launch a third time as clusterc , the shared loadbalancer will be renamed again.
So the ownership will be for the last runner of ensureOctaviaLoadBalancer
The text was updated successfully, but these errors were encountered:
Hello,
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
While testing shared loadbalancers, i think i discovered a regression since this PR.
A shared loadbalancer is renamed due to this if. What happens here is :
We enter the
ensureOctaviaLoadBalancer
function asclusterb
with a shared loadbalancer named :kube_service_clustera_kns_fakeservice
At the end we can see the cluster has been renamed :
kube_service_clusterb_kns_fakeservice
.And we have the event :
Warning LoadBalancerRename Loadbalancer fakeloadbalancerid has a name of kube_service_clustera_kns_fakeservice with incorrect cluster-name component. Renaming it to kube_service_clusterb_kns_fakeservice.
The tags has been changed too :
["kube_service_clustera_kns_fakeservice","clustera","kube_service_clusterb_kns_fakeservice"]
become
["kube_service_clusterb_kns_fakeservice","clustera","kube_service_clusterb_kns_fakeservice"]
I created a test that reproduce the regression.
Didn't test if it's the case , but i suspect that if we launch a third time as
clusterc
, the shared loadbalancer will be renamed again.So the ownership will be for the last runner of
ensureOctaviaLoadBalancer
The text was updated successfully, but these errors were encountered: