Skip to content

OCPBUGS-18052: feat: added logic to handle legacy sno install #778

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

Conversation

eggfoobar
Copy link
Contributor

added legacy check method to generate MCs for SNO installs using the old MC method
updated documentation to correctly refer to feature as 4.14

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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 31, 2023
@openshift-ci-robot
Copy link
Contributor

@eggfoobar: This pull request references Jira Issue OCPBUGS-18052, which is invalid:

  • expected the bug to target the "4.14.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:

added legacy check method to generate MCs for SNO installs using the old MC method
updated documentation to correctly refer to feature as 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-ci openshift-ci bot requested review from dagrayvid and yanirq August 31, 2023 18:39
@eggfoobar
Copy link
Contributor Author

/hold

Validating fix

@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 Aug 31, 2023
updated documentation to correctly refer to feature as 4.14
changed variables to be more consistent with current naming pattern

Signed-off-by: ehila <ehila@redhat.com>
@eggfoobar eggfoobar force-pushed the ocpbugs-18052-workload-pinning branch from 521971e to f82e9dc Compare August 31, 2023 22:05
@eggfoobar
Copy link
Contributor Author

/unhold

Verified that the fix worked with a build from cluster bot.

@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 Aug 31, 2023
@yanirq
Copy link
Contributor

yanirq commented Sep 1, 2023

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Sep 1, 2023
@yanirq
Copy link
Contributor

yanirq commented Sep 1, 2023

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eggfoobar, yanirq

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 Sep 1, 2023
@yanirq
Copy link
Contributor

yanirq commented Sep 1, 2023

/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 Sep 1, 2023
@openshift-ci-robot
Copy link
Contributor

@yanirq: This pull request references Jira Issue OCPBUGS-18052, which is valid. The bug has been moved to the POST state.

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 ASSIGNED, 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 (liqcui@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 kubernetes/test-infra repository.

@yanirq
Copy link
Contributor

yanirq commented Sep 1, 2023

/cc @MarSik @ffromani

@openshift-ci openshift-ci bot requested review from ffromani and MarSik September 1, 2023 01:51
Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

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

thanks @eggfoobar , makes sense to me. The only gap I see is that we should improve the testing side

Signed-off-by: ehila <ehila@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2023

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

@yanirq
Copy link
Contributor

yanirq commented Sep 3, 2023

@eggfoobar Thank you for the PR and the added e2e tests.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2023
@openshift-merge-robot openshift-merge-robot merged commit 445cc60 into openshift:master Sep 3, 2023
@openshift-ci-robot
Copy link
Contributor

@eggfoobar: Jira Issue OCPBUGS-18052: All pull requests linked via external trackers have merged:

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

In response to this:

added legacy check method to generate MCs for SNO installs using the old MC method
updated documentation to correctly refer to feature as 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.

Tal-or added a commit to Tal-or/cluster-node-tuning-operator that referenced this pull request Oct 12, 2023
When openshift#778 got merged
The directory layout has changed and broke the `render-sync`  make target.
This patch should fix it.

Signed-off-by: Talor Itzhak <titzhak@redhat.com>
openshift-ci bot pushed a commit that referenced this pull request Oct 13, 2023
When #778 got merged
The directory layout has changed and broke the `render-sync`  make target.
This patch should fix it.

Signed-off-by: Talor Itzhak <titzhak@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/cluster-node-tuning-operator that referenced this pull request Oct 15, 2023
When openshift#778 got merged
The directory layout has changed and broke the `render-sync`  make target.
This patch should fix it.

Signed-off-by: Talor Itzhak <titzhak@redhat.com>
openshift-merge-bot bot pushed a commit that referenced this pull request Nov 14, 2023
When #778 got merged
The directory layout has changed and broke the `render-sync`  make target.
This patch should fix it.

Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Co-authored-by: Talor Itzhak <titzhak@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-critical Referenced Jira bug's severity is critical 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants