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-25696: Apply Scheduling Configuration for kCCM #3382

Merged

Conversation

orenc1
Copy link
Contributor

@orenc1 orenc1 commented Jan 8, 2024

What this PR does / why we need it:

kCCM deployment was not respecting the node selector configured at hcp.spec.nodeSelector that was set with --node-selector flag in the create cli command. This PR fixes the issue, by applying SetDefaults() to the deploymentConfig, which sets the node selector along with other required configurations (e.g. tolerations, affinity, replica count, etc.)

Which issue(s) this PR fixes
Fixes # https://issues.redhat.com/browse/OCPBUGS-25696

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

@openshift-ci-robot openshift-ci-robot added 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 Jan 8, 2024
@openshift-ci-robot
Copy link

@orenc1: This pull request references Jira Issue OCPBUGS-25696, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

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:

What this PR does / why we need it:

kCCM deployment was not respecting the node selector configured at hcp.spec.nodeSelector that was set with --node-selector flag in the create cli command. This PR fixes the issue, by applying SetDefaults() to the deploymentConfig, which sets the node selector along with other required configurations (e.g. tolerations, affinity, replica count, etc.)

Which issue(s) this PR fixes
Fixes # https://issues.redhat.com/browse/OCPBUGS-25696

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release and removed do-not-merge/needs-area labels Jan 8, 2024
@orenc1
Copy link
Contributor Author

orenc1 commented Jan 8, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 8, 2024
@openshift-ci-robot
Copy link

@orenc1: This pull request references Jira Issue OCPBUGS-25696, which is valid.

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

No GitHub users were found matching the public email listed for the QA contact in Jira (yli2@redhat.com), skipping review request.

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

@davidvossel davidvossel left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 8, 2024
Copy link
Contributor

openshift-ci bot commented Jan 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davidvossel, orenc1

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 Jan 8, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 660b17b and 2 for PR HEAD a48a07f in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 90cd1cc and 1 for PR HEAD a48a07f in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 447d1bb and 0 for PR HEAD a48a07f in total

@openshift-ci-robot
Copy link

/hold

Revision a48a07f was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 9, 2024
@orenc1
Copy link
Contributor Author

orenc1 commented Jan 9, 2024

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 9, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 447d1bb and 2 for PR HEAD a48a07f in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6a632af and 1 for PR HEAD a48a07f in total

@orenc1
Copy link
Contributor Author

orenc1 commented Jan 10, 2024

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 654cc64 and 0 for PR HEAD a48a07f in total

https://issues.redhat.com/browse/OCPBUGS-25696
kCCM deployment was not respecting the node selector configured at hcp.spec.nodeSelector that was set with --node-selector flag in the create cli command.
This PR fixes the issue, by applying 'SetDefaults()' to the deploymentConfig, which sets the node selector along with other required configurations (e.g. tolerations, affinity, replica count, etc.)
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 11, 2024
Copy link

netlify bot commented Jan 11, 2024

Deploy Preview for hypershift-docs ready!

Name Link
🔨 Latest commit eecee03
🔍 Latest deploy log https://app.netlify.com/sites/hypershift-docs/deploys/659fa7fe0f67540008b0a666
😎 Deploy Preview https://deploy-preview-3382--hypershift-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@davidvossel davidvossel left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 11, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7690059 and 2 for PR HEAD eecee03 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4191e17 and 1 for PR HEAD eecee03 in total

Copy link
Contributor

openshift-ci bot commented Jan 12, 2024

@orenc1: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit ad0630b into openshift:main Jan 12, 2024
12 checks passed
@openshift-ci-robot
Copy link

@orenc1: Jira Issue OCPBUGS-25696: All pull requests linked via external trackers have merged:

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

In response to this:

What this PR does / why we need it:

kCCM deployment was not respecting the node selector configured at hcp.spec.nodeSelector that was set with --node-selector flag in the create cli command. This PR fixes the issue, by applying SetDefaults() to the deploymentConfig, which sets the node selector along with other required configurations (e.g. tolerations, affinity, replica count, etc.)

Which issue(s) this PR fixes
Fixes # https://issues.redhat.com/browse/OCPBUGS-25696

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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 openshift-eng/jira-lifecycle-plugin repository.

@orenc1 orenc1 deleted the missing_nodeselector_kccm branch January 12, 2024 09:55
@orenc1
Copy link
Contributor Author

orenc1 commented Jan 12, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot

@orenc1: new pull request created: #3417

In response to this:

/cherry-pick release-4.15

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.

@orenc1
Copy link
Contributor Author

orenc1 commented Jan 12, 2024

/cherry-pick release-4.14

@openshift-cherrypick-robot

@orenc1: new pull request created: #3418

In response to this:

/cherry-pick release-4.14

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-01-14-231715

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/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants