Retry deleting the LB if 204 is returned

[nilo19]

What happened:

Deleting LB will sometimes succeed with code 204, but the request doesn't reach NRP side, and the LB doesn't get deleted. We should try to GET the LB to see if it still exists. If so, we should retry deleting it.

What you expected to happen:

The LB should be deleted.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others:

[uroy-personal]

Hi @nilo19 , I am interested in working on this issue. Would appreciate If you could provide more info and guidance in implementing it.

[amargherio]

@uroy-personal are you still interested in working on this issue? If not, @nilo19 I'd like to take this work on if it hasn't been addressed already.

[amargherio]

After checking with @nilo19 and a bit of discussion, it appears that this behavior hasn't been observed for a while now. This might be safe to close and could be reopened if the behavior comes up again.

[feiskyer]

Thanks for the discussion and conclusion!

/close

[k8s-ci-robot]

@feiskyer: Closing this issue.

In response to this:

Thanks for the discussion and conclusion!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.