OCPBUGS-47658: [release-4.16][manual]: Fix context deadlines in ExecCommandOnPod()

[Tal-or]

Manual and partial backport of #1189

[Tal-or]

We should backport this PR up until 4.14.

I see similar symptoms in: openshift-kni/cnf-features-deploy#2135

[Tal-or]

/cc @yanirq @jmencak

[yanirq]

/jira cherry-pick OCPBUGS-43877

[openshift-ci-robot]

@yanirq: Jira Issue OCPBUGS-43877 has been cloned as Jira Issue OCPBUGS-47658. Will retitle bug to link to clone.
/retitle OCPBUGS-47658: [release-4.16][manual]: Fix context deadlines in ExecCommandOnPod()

In response to this:

/jira cherry-pick OCPBUGS-43877

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]

@Tal-or: This pull request references Jira Issue OCPBUGS-47658, 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.16.z) matches configured target version for branch (4.16.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-43877 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-43877 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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

In response to this:

Manual and partial backport of #1189

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]

/approve
/lgtm

[Tal-or]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@Tal-or: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.15

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.

[Tal-or]

/hold

I want to check if this PR fixes the issue on openshift-kni/cnf-features-deploy#2135

[openshift-ci]

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

[Tal-or]

/hold cancel
It does

[jmencak]

Thank you for the backport.
/lgtm
/approve
/backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, Tal-or, 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:

• OWNERS [jmencak,yanirq]

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

[mrniranjan]

/label cherry-pick-approved

[yanirq]

/label backport-risk-assessed

[openshift-ci-robot]

@Tal-or: Jira Issue OCPBUGS-47658: All pull requests linked via external trackers have merged:

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

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

In response to this:

Manual and partial backport of #1189

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-cherrypick-robot]

@Tal-or: #1263 failed to apply on top of branch "release-4.15":

Applying: Fix context deadlines in ExecCommandOnPod()
Using index info to reconstruct a base tree...
M	test/e2e/performanceprofile/functests/utils/nodes/nodes.go
M	test/e2e/performanceprofile/functests/utils/pods/pods.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/performanceprofile/functests/utils/pods/pods.go
CONFLICT (content): Merge conflict in test/e2e/performanceprofile/functests/utils/pods/pods.go
Auto-merging test/e2e/performanceprofile/functests/utils/nodes/nodes.go
CONFLICT (content): Merge conflict in test/e2e/performanceprofile/functests/utils/nodes/nodes.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 Fix context deadlines in ExecCommandOnPod()

In response to this:

/cherry-pick release-4.15

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

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