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

BZ1714769: fix kubeletconfig with empty MCPs status updates #811

Merged
merged 1 commit into from
Jun 3, 2019

Conversation

rphillips
Copy link
Contributor

- What I did
Do not requeue the key if there are zero MCPs. Prevents multiple status updates and will not succeed.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1714769

- How to verify it

- Description for the changelog

Fix status updates with kubeletconfigs with zero MCPs.

@rphillips
Copy link
Contributor Author

/cc @sjenning

@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 3, 2019
@@ -59,6 +60,9 @@ var updateBackoff = wait.Backoff{
Jitter: 1.0,
}

// ErrCouldNotFindMCPSet Error if no MCPs could be found
var ErrCouldNotFindMCPSet = errors.New("could not find any MachineConfigPool set for KubeletConfig")
Copy link
Member

Choose a reason for hiding this comment

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

does this need to be exported?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it doesn't.... I have removed the export in the force push.

Do not requeue the key if there are zero MCPs. Prevents multiple status
updates and will not succeed.

ref: https://bugzilla.redhat.com/show_bug.cgi?id=1714769
@rphillips rphillips changed the title BZ1714769: fix kubeletconfig zero MCP errors BZ1714769: fix kubeletconfig with empty MCPs status updates Jun 3, 2019
@sjenning
Copy link
Contributor

sjenning commented Jun 3, 2019

lgtm, thanks!

@runcom
Copy link
Member

runcom commented Jun 3, 2019

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rphillips, runcom

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2019
@runcom
Copy link
Member

runcom commented Jun 3, 2019

registry hiccups in CI :(

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit acf5b49 into openshift:master Jun 3, 2019
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. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants