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-46584: Adjust Workload Hints test cases based on Intel or AMD #1258

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

mrniranjan
Copy link
Contributor

This PR adds utility functions to get Cpu Vendor (intel or AMD) in case of x86_64.
Also Adjust Workload Hints test cases where kernel Args are adjusted based on Intel or AMD.

@openshift-ci openshift-ci bot requested review from Tal-or and yanirq December 18, 2024 16:05
@mrniranjan mrniranjan changed the title Adjust Workload Hints test cases based on Intel or AMD OCPBUGS-46584: Adjust Workload Hints test cases based on Intel or AMD Dec 18, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2024
@openshift-ci-robot
Copy link
Contributor

@mrniranjan: This pull request references Jira Issue OCPBUGS-46584, 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.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mrniranjan

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

In response to this:

This PR adds utility functions to get Cpu Vendor (intel or AMD) in case of x86_64.
Also Adjust Workload Hints test cases where kernel Args are adjusted based on Intel or AMD.

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-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 Dec 18, 2024
Copy link
Contributor

openshift-ci bot commented Dec 18, 2024

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: mrniranjan.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@mrniranjan: This pull request references Jira Issue OCPBUGS-46584, 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.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mrniranjan

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

In response to this:

This PR adds utility functions to get Cpu Vendor (intel or AMD) in case of x86_64.
Also Adjust Workload Hints test cases where kernel Args are adjusted based on Intel or AMD.

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.

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-sigs/prow repository.

if isIntel {
Expect(cmdline).To(ContainSubstring("intel_pstate=passive"))
Expect(cmdline).ToNot(ContainSubstring("intel_pstate=active"))
} else {
Copy link
Contributor

Choose a reason for hiding this comment

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

Would isAMD be more descriptive with an else that throws an error? Just in case we get ARM machines in the future?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ack, i will add it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed in the latest commit

@mrniranjan
Copy link
Contributor Author

/retest-required

@mrniranjan mrniranjan force-pushed the check_cpu_vendor branch 2 times, most recently from 50ded99 to 9d47c77 Compare December 19, 2024 02:47
@mrniranjan
Copy link
Contributor Author

/retest-required

Niranjan M.R added 3 commits December 19, 2024 12:24
We use lscpu output and check Vendor ID to determine
if the system is AMD or Intel.

Signed-off-by: Niranjan M.R <[email protected]>
Adjust Workload Hints E2E test cases to verify kernel
parameters depending on the Vendor in the case of x86_64
where kernel args are changed based on Intel or AMD.

Signed-off-by: Niranjan M.R <[email protected]>
Copy link
Contributor

@MarSik MarSik 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 Dec 20, 2024
Copy link
Contributor

openshift-ci bot commented Dec 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MarSik, mrniranjan

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 Dec 20, 2024
@yanirq
Copy link
Contributor

yanirq commented Dec 21, 2024

/label acknowledge-critical-fixes-only

test only change

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Dec 21, 2024
@mrniranjan
Copy link
Contributor Author

@yanirq sorry, i am adding a hold due to a bug in my patch

@mrniranjan
Copy link
Contributor Author

/hold

@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 Dec 21, 2024
remove duplicate intel_pstate=passive from kernelParameters
string slice as it's already added if system is intel

Signed-off-by: Niranjan M.R <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 21, 2024
Copy link
Contributor

openshift-ci bot commented Dec 21, 2024

New changes are detected. LGTM label has been removed.

@mrniranjan
Copy link
Contributor Author

/hold cancel

@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 Dec 21, 2024
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/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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants