Skip to content

Conversation

@jlojosnegros
Copy link
Contributor

This command should render a MC from the available sources. PerformanceProfile is a source, but it is not mandatory.

So, as there are scenarios where this command should work with no additional PP let's the command proceed even if there is no PP

This command should render a MC from the available sources.
PerformanceProfile is a source, but it is not mandatory.

So, as there are scenarios where this command should work with no
additional PP let's the command proceed even if there is no PP

Signed-off-by: Jose Luis Ojosnegros Manchón <[email protected]>
@openshift-ci openshift-ci bot requested review from MarSik and kpouget January 22, 2024 10:33
@yanirq
Copy link
Contributor

yanirq commented Jan 22, 2024

The meaning of "additional" is a bit obscured here ? Can we use the render command without a performance profile at all ?

@jlojosnegros
Copy link
Contributor Author

jlojosnegros commented Jan 23, 2024

The meaning of "additional" is a bit obscured here ? Can we use the render command without a performance profile at all ?

Well per the last discussion we had, yes.
This render command should render a MC with the kernel args from all available sources.
PerformanceProfile is another source but not a mandatory one.

Please @MarSik keep me honest here.

@MarSik
Copy link
Contributor

MarSik commented Jan 23, 2024

@yanirq Yep, it is a tuned render after all. We only need to know the perf profiles to be able to collect all the generated tuned objects. But when there are no extra tuneds, NTO still ships the stock openshift-node Tuned with the proper recommendation selectors.

So the logic still works fine, even though there are no extra kernel args atm.

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

openshift-ci bot commented Jan 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 23, 2024
@jlojosnegros
Copy link
Contributor Author

/test e2e-aws-ovn-techpreview

@jlojosnegros
Copy link
Contributor Author

/test e2e-gcp-pao-updating-profile

@jlojosnegros jlojosnegros changed the title Render MC without additional PP CNF-10170: Render MC without additional PP Jan 24, 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 Jan 24, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 24, 2024

@jlojosnegros: This pull request references CNF-10170 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.16." or "openshift-4.16.", but it targets "openshift-4.15" instead.

Details

In response to this:

This command should render a MC from the available sources. PerformanceProfile is a source, but it is not mandatory.

So, as there are scenarios where this command should work with no additional PP let's the command proceed even if there is no PP

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

/retest-required

Remaining retests: 0 against base HEAD fd8b0be and 2 for PR HEAD a50a527 in total

@jlojosnegros
Copy link
Contributor Author

/hold
Need to rebase once #929 is merged.

@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 25, 2024
@jlojosnegros
Copy link
Contributor Author

/hold cancel
as #929 has been already merged.

@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 30, 2024
@jlojosnegros
Copy link
Contributor Author

/test e2e-gcp-pao-updating-profile

@jlojosnegros
Copy link
Contributor Author

/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 Jan 30, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2024

@jlojosnegros: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202401302041.p0.g74ecaaa.assembly.stream for distgit cluster-node-tuning-operator.
All builds following this will include this PR.

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-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.

5 participants