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-13330: Use RHEL9 as a base #829

Merged
merged 1 commit into from Oct 25, 2023

Conversation

jmencak
Copy link
Contributor

@jmencak jmencak commented Oct 16, 2023

x86_energy_perf_policy from RHEL8 causes a kernel taint on RHEL9 kernels. This is a problem for CNF certifications. Switch the NTO base to RHEL9 so that we use an up-to-date x86_energy_perf_policy aligned with RHEL9 kernels.

Resolves: OCPBUGS-13330

x86_energy_perf_policy from RHEL8 causes a kernel taint on RHEL9
kernels.  This is a problem for CNF certifications.  Switch the NTO base
to RHEL9 so that we use an up-to-date x86_energy_perf_policy aligned
with RHEL9 kernels.

Resolves: OCPBUGS-13330
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 16, 2023
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 16, 2023
@jmencak jmencak changed the title WiP: Use RHEL9 as a base Use RHEL9 as a base Oct 17, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 17, 2023
Copy link
Contributor

@jlojosnegros jlojosnegros 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 Oct 20, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlojosnegros, jmencak

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

@jmencak
Copy link
Contributor Author

jmencak commented Oct 20, 2023

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 20, 2023
@jmencak jmencak changed the title Use RHEL9 as a base OCPBUGS-13330: Use RHEL9 as a base Oct 24, 2023
@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 Oct 24, 2023
@openshift-ci-robot
Copy link
Contributor

@jmencak: This pull request references Jira Issue OCPBUGS-13330, which is invalid:

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

x86_energy_perf_policy from RHEL8 causes a kernel taint on RHEL9 kernels. This is a problem for CNF certifications. Switch the NTO base to RHEL9 so that we use an up-to-date x86_energy_perf_policy aligned with RHEL9 kernels.

Resolves: OCPBUGS-13330

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.

@jmencak
Copy link
Contributor Author

jmencak commented Oct 24, 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 Oct 24, 2023
@openshift-ci-robot
Copy link
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-21772 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-21772 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

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.

@jmencak
Copy link
Contributor Author

jmencak commented Oct 24, 2023

@liqcui , can we please have cherry-pick-approved label for this?

@liqcui
Copy link

liqcui commented Oct 25, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 25, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8d94974 and 2 for PR HEAD 8ea098e in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2023

@jmencak: 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-ci openshift-ci bot merged commit fad5b5c into openshift:release-4.13 Oct 25, 2023
11 checks passed
@openshift-ci-robot
Copy link
Contributor

@jmencak: An error was encountered updating to the MODIFIED state for bug OCPBUGS-13330 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. It seems that you have tried to perform a workflow operation (MODIFIED) that is not valid for the current state of this issue (OCPBUGS-13330). The likely cause is that somebody has changed the issue recently, please look at the issue history for details.: request failed. Please analyze the request body for more details. Status code: 400:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

x86_energy_perf_policy from RHEL8 causes a kernel taint on RHEL9 kernels. This is a problem for CNF certifications. Switch the NTO base to RHEL9 so that we use an up-to-date x86_energy_perf_policy aligned with RHEL9 kernels.

Resolves: OCPBUGS-13330

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.

@jmencak jmencak deleted the 4.13-RHEL9-base branch October 25, 2023 10:00
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

4 participants