-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In tree 1.21.2 Windows ELB fails to reconcile #706
In tree 1.21.2 Windows ELB fails to reconcile #706
Comments
The same errors happens with k8s 1.20.8 |
/assign @nilo19 |
Can we add a windows + standalone vm check-in or regular test? |
@CecileRobertMichon could you test out-of-tree ccm, which contains the fix. cloud-provider-azure/pkg/provider/azure_vmss.go Line 1375 in e69e42b
|
If it works, I will cherry pick it into k/k. |
opened #705
will do |
@nilo19 I can confirm I cannot repro this with out-of-tree. This only happens with in-tree. Please go ahead and cherry-pick in k/k. |
@nilo19 we can also repro this with Linux
|
What happened:
With standalone VMs (CAPZ cluster) using vmType "vmss", can repro 100% of the time using in tree cloud provider k8s 1.21.2:
Linux ILB + ELB and Windows ILB reconcile successfully:
I0714 13:08:21.026400 1 azure_loadbalancer.go:1502] reconcileLoadBalancer for service(default/webroha7z-ilb): lb(capz-e2e-3k3e35-internal) finished
I0714 13:08:43.680525 1 azure_loadbalancer.go:1502] reconcileLoadBalancer for service(default/webroha7z-elb): lb(capz-e2e-3k3e35) finished
I0714 13:11:36.489670 1 azure_loadbalancer.go:1502] reconcileLoadBalancer for service(default/web-windowsat01ng-ilb): lb(capz-e2e-3k3e35-internal) finished
Then Windows ELB fails with this error:
Full logs: https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-azure/1524/pull-cluster-api-provider-azure-e2e-windows/1415291396272689152/artifacts/clusters/capz-e2e-3k3e35/kube-system/kube-controller-manager-capz-e2e-3k3e35-control-plane-bhf94/kube-controller-manager.log
What you expected to happen:
How to reproduce it:
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: