[release-4.19] OCPBUGS-58402: Do not add iommu.passthrough to ARM by default

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1354

/assign yanirq

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-52853 has been cloned as Jira Issue OCPBUGS-58402. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-58402: Do not add iommu.passthrough to ARM by default

Details

In response to this:

This is an automated cherry-pick of #1354

/assign yanirq

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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-58402, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-52853 to target a version in 4.20.0, but it targets "4.20" instead

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.

Details

In response to this:

This is an automated cherry-pick of #1354

/assign yanirq

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.

[yanirq]

/lgtm
/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yanirq

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:

• OWNERS [yanirq]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[yanirq]

/jira refresh

[openshift-ci-robot]

@yanirq: This pull request references Jira Issue OCPBUGS-58402, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

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.

[yanirq]

/jira refresh

[openshift-ci-robot]

@yanirq: This pull request references Jira Issue OCPBUGS-58402, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

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.

[yanirq]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.z) matches configured target version for branch (4.19.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-52853 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-52853 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

Requesting review from QA contact:
/cc @mrniranjan

Details

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.

[openshift-ci]

@openshift-cherrypick-robot: 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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-58402: All pull requests linked via external trackers have merged:

• openshift/cluster-node-tuning-operator#1358

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

Details

In response to this:

This is an automated cherry-pick of #1354

/assign yanirq

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: cluster-node-tuning-operator
This PR has been included in build cluster-node-tuning-operator-container-v4.19.0-202507102007.p0.g61b6637.assembly.stream.el9.
All builds following this will include this PR.

[yanirq]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@yanirq: #1358 failed to apply on top of branch "release-4.18":

Applying: OCPBUGS-52853: Do not add iommu.passthrough to ARM by default
Using index info to reconstruct a base tree...
M	pkg/performanceprofile/controller/performanceprofile/components/tuned/tuned_test.go
A	test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_tuned.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_tuned.yaml deleted in HEAD and modified in OCPBUGS-52853: Do not add iommu.passthrough to ARM by default. Version OCPBUGS-52853: Do not add iommu.passthrough to ARM by default of test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_tuned.yaml left in tree.
Auto-merging pkg/performanceprofile/controller/performanceprofile/components/tuned/tuned_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-52853: Do not add iommu.passthrough to ARM by default

Details

In response to this:

/cherry-pick release-4.18

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.