Change:
return service, err } <ins> func (sr *ServiceRegistryStorage) deleteExternalLoadBalancer(service *api.Service) error { if !service.CreateExternalLoadBalancer || sr.cloud == nil { return nil } zones, ok := sr.cloud.Zones() if !ok { // We failed to get zone enumerator. // As this should have failed when we tried in "create" too, // assume external load balancer was never created. return nil } balancer, ok := sr.cloud.TCPLoadBalancer() if !ok { // See comment above. return nil } zone, err := zones.GetZone() if err != nil { return err } if err := balancer.DeleteTCPLoadBalancer(service.JSONBase.ID, zone); err != nil { return err } return nil } </ins> func (sr *ServiceRegistryStorage) Delete(id string) (<-chan interface{}, error) { service, err := sr.registry.GetService(id) if err != nil { return nil, err } return apiserver.MakeAsync(func() (interface{}, error) { <del> if service.CreateExternalLoadBalancer { var balancer cloudprovider.TCPLoadBalancer var ok bool if sr.cloud != nil { balancer, ok = sr.cloud.TCPLoadBalancer() } if ok && balancer != nil { err = balancer.DeleteTCPLoadBalancer(id, "us-central1") if err != nil { return nil, err } } } </del> <ins> sr.deleteExternalLoadBalancer(service) </ins> return api.Status{Status: api.StatusSuccess}, sr.registry.DeleteService(id) }), nil }

Discussion:
pull-kubernetes-e2e-azure-disk-windows pull-kubernetes-e2e-azure-disk-windows It seems caused by connection failed: from kubelet logs: This repeats until timeout
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig windows
/area providers/azure
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /area providers/azure Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Last run (): The run before (): no code changes in between
Now my PR passed the lane without any code changes (just yet another retest):
note that is not a presubmit for merge, or else it would show: <img width="89" alt="Screen Shot 2021-03-08 at 11 30 57 PM" src="https://user-"non-required presubmits can be bypassed with , but are generally worth looking at first
/assign Can you take a look?
There's something odd going on here. As the test description indicates, it deletes the pod for the StatefulSet and expects it to be recreated. When the kubelet attempts to recreate the pod, however, the mount point for the volume is no longer there. From the log above, we can see the pod was deleted succesfully. It was then rescheduled but failed because the volume mount point does not exist. In the kubelet logs, we see the successful mount for the initial pod creation: We then see the delete of the pod and the failed attempt to recreate it: Finally during cleanup, we see a failure during unmount the volume because the mount point does not exist: None of the other collected logs show what happened to the original mount point.