Skip to content
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

fix: consolidate logs for instance not found error #105188

Merged
merged 2 commits into from Sep 29, 2021

Conversation

nilo19
Copy link
Member

@nilo19 nilo19 commented Sep 22, 2021

What type of PR is this?

/kind bug

What this PR does / why we need it:

fix: consolidate logs for instance not found error

  • Ignore the instance not found error when cleaning up unwanted nodes from LB backend pool
  • Log node name when "instance not found" errors happen
  • skip not found nodes when reconciling LB backend address pools

Which issue(s) this PR fixes:

Fixes kubernetes-sigs/cloud-provider-azure#789

Special notes for your reviewer:

Does this PR introduce a user-facing change?

fix: consolidate logs for instance not found error
fix: skip not found nodes when reconciling LB backend address pools

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


/sig cloud-provider
/area provider/azure
/priority critical-urgent
/triage accepted
cc @feiskyer

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. area/provider/azure Issues or PRs related to azure provider do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/cloudprovider and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 22, 2021
Copy link
Member

@feiskyer feiskyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/retest

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 22, 2021
@feiskyer
Copy link
Member

Need approval from cloud provider
/assign @andrewsykim

@nilo19
Copy link
Member Author

nilo19 commented Sep 23, 2021

/retest

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 29, 2021
@feiskyer
Copy link
Member

/retest
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 29, 2021
@nilo19
Copy link
Member Author

nilo19 commented Sep 29, 2021

/retest

@@ -59,7 +59,7 @@ func TestGetVirtualMachineWithRetry(t *testing.T) {
},
{
vmClientErr: &retry.Error{HTTPStatusCode: http.StatusInternalServerError},
expectedErr: fmt.Errorf("Retriable: false, RetryAfter: 0s, HTTPStatusCode: 500, RawError: <nil>"),
expectedErr: fmt.Errorf("Retriable: false, RetryAfter: 0s, HTTPStatusCode: 500, RawError: %w", error(nil)),
Copy link
Member

@cheftako cheftako Sep 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure you want %w on something which I don't believe can be a wrapped error. Maybe just %v?

@cheftako
Copy link
Member

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheftako, feiskyer, nilo19

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2021
@k8s-ci-robot k8s-ci-robot merged commit 1ad3e14 into kubernetes:master Sep 29, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Sep 29, 2021
@nilo19 nilo19 deleted the bug/cherry-pick-794 branch September 30, 2021 02:50
k8s-ci-robot added a commit that referenced this pull request Oct 13, 2021
…88-upstream-release-1.20

Automated cherry pick of #105188: fix: consolidate logs for instance not found error
k8s-ci-robot added a commit that referenced this pull request Oct 13, 2021
…88-upstream-release-1.21

Cherry pick of #105188 and #98350 to release 1.21
k8s-ci-robot added a commit that referenced this pull request Oct 13, 2021
…88-upstream-release-1.22

Automated cherry pick of #105188: fix: consolidate logs for instance not found error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/cloudprovider area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ignore the instance not found error when cleaning up unwanted nodes from LB backend pool
5 participants