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

OCPBUGS-11486: fix: correctly determine master nodes by label for SNO #376

Conversation

jakobmoellerdev
Copy link
Contributor

Uses https://kubernetes.io/docs/reference/labels-annotations-taints/#node-role-kubernetes-io-control-plane to discover master nodes instead of simply checking if there is one node.

also adds tests for various node configurations in the Wild and moves the resolve logic out of main.go

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 3, 2023
@openshift-ci-robot
Copy link

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-11486, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Uses https://kubernetes.io/docs/reference/labels-annotations-taints/#node-role-kubernetes-io-control-plane to discover master nodes instead of simply checking if there is one node.

also adds tests for various node configurations in the Wild and moves the resolve logic out of main.go

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.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 3, 2023
@jakobmoellerdev
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 3, 2023
@openshift-ci-robot
Copy link

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-11486, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @radeore

In response to this:

/jira refresh

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 3, 2023
@openshift-ci openshift-ci bot requested a review from radeore August 3, 2023 13:15
also adds tests for various node configurations in the Wild

Signed-off-by: jakobmoellerdev <jmoller@redhat.com>
@jakobmoellerdev jakobmoellerdev force-pushed the OCPBUGS-11486-master-only-sno-check branch from 9cd53c0 to cc4ef90 Compare August 3, 2023 13:16
@jeff-roche
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 3, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev, jeff-roche

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2023
@codecov-commenter
Copy link

Codecov Report

Merging #376 (cc4ef90) into main (a962b90) will increase coverage by 40.13%.
Report is 6 commits behind head on main.
The diff coverage is 57.57%.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main     #376       +/-   ##
===========================================
+ Coverage   16.59%   56.73%   +40.13%     
===========================================
  Files          24       25        +1     
  Lines        2061     2094       +33     
===========================================
+ Hits          342     1188      +846     
+ Misses       1693      822      -871     
- Partials       26       84       +58     
Files Changed Coverage Δ
pkg/cluster/leaderelection.go 57.57% <57.57%> (ø)

... and 11 files with indirect coverage changes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 3, 2023

@jakobmoellerdev: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@jeff-roche jeff-roche merged commit 6f10571 into openshift:main Aug 3, 2023
@openshift-ci-robot
Copy link

@jakobmoellerdev: Jira Issue OCPBUGS-11486: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-11486 has been moved to the MODIFIED state.

In response to this:

Uses https://kubernetes.io/docs/reference/labels-annotations-taints/#node-role-kubernetes-io-control-plane to discover master nodes instead of simply checking if there is one node.

also adds tests for various node configurations in the Wild and moves the resolve logic out of main.go

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.

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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants