[release-4.19] OCPBUGS-59633: E2E add test to verify guaranteed pod is running after kubelet restart #1365

openshift-cherrypick-robot · 2025-07-22T12:22:46Z

This is an automated cherry-pick of #1361

/assign mrniranjan

This PR addresses issue where we are verifying if the cpu manager state file is same after kubelet restart while we are verifying the above, we are not checking if Guranteed pod started before kubelet restart is also still running. Refer: https://issues.redhat.com/browse/OCPBUGS-43280 Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>

Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>

openshift-ci-robot · 2025-07-22T12:22:57Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-59354 has been cloned as Jira Issue OCPBUGS-59633. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-59633: E2E add test to verify guaranteed pod is running after kubelet restart

Details

In response to this:

This is an automated cherry-pick of #1361

/assign mrniranjan

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 · 2025-07-22T12:23:27Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-59633, which is invalid:

expected dependent Jira Issue OCPBUGS-59354 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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 #1361

/assign mrniranjan

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.

mrniranjan · 2025-08-07T15:55:18Z

/jira refresh

openshift-ci-robot · 2025-08-07T15:55:26Z

@mrniranjan: This pull request references Jira Issue OCPBUGS-59633, 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-59354 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-59354 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.

MarSik · 2025-08-25T13:47:06Z

test/e2e/performanceprofile/functests/1_performance/cpu_management.go

+						}
+					}
+					return nil
+				}).WithTimeout(5*time.Minute).WithPolling(10*time.Second).Should(Succeed(), "test pod should come back after kubelet restart")


It is not a bug, but the pod never went anywhere :) It should be still present and up.

Yes, we are only checking if the pod is still in running state after kubelet restart

MarSik

/lgtm

openshift-ci · 2025-08-25T13:48:34Z

[APPROVALNOTIFIER] This PR is APPROVED

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

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~~ [MarSik]

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

MarSik · 2025-09-01T09:37:42Z

/label backport-risk-assessed

openshift-ci · 2025-09-01T13:35:25Z

@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 · 2025-09-01T13:39:43Z

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

openshift/cluster-node-tuning-operator#1365

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

Details

In response to this:

This is an automated cherry-pick of #1361

/assign mrniranjan

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 · 2025-09-01T17:00:47Z

[ART PR BUILD NOTIFIER]

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

openshift-merge-robot · 2025-09-03T06:12:13Z

Fix included in accepted release 4.19.0-0.nightly-2025-09-02-192040

mrniranjan · 2025-12-16T10:56:30Z

/cherry-pick release-4.18

openshift-cherrypick-robot · 2025-12-16T10:57:26Z

@mrniranjan: new pull request created: #1448

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.

Niranjan M.R added 3 commits July 22, 2025 12:22

avoid using indirect references and test negative pod status condition

3f02e16

Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>

typo fix and add more debug when pod fails

2a1974f

Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>

openshift-cherrypick-robot assigned mrniranjan Jul 22, 2025

openshift-cherrypick-robot mentioned this pull request Jul 22, 2025

OCPBUGS-59354: E2E add test to verify guaranteed pod is running after kubelet restart #1361

Merged

openshift-ci bot changed the title ~~[release-4.19] OCPBUGS-59354: E2E add test to verify guaranteed pod is running after kubelet restart~~ [release-4.19] OCPBUGS-59633: E2E add test to verify guaranteed pod is running after kubelet restart Jul 22, 2025

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 Jul 22, 2025

openshift-ci bot requested review from ffromani and yanirq July 22, 2025 12:24

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 Aug 7, 2025

openshift-ci bot requested a review from mrniranjan August 7, 2025 15:55

MarSik reviewed Aug 25, 2025

View reviewed changes

MarSik approved these changes Aug 25, 2025

View reviewed changes

openshift-ci bot assigned MarSik Aug 25, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 25, 2025

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 1, 2025

openshift-merge-bot bot merged commit d8f7a16 into openshift:release-4.19 Sep 1, 2025
19 checks passed

openshift-cherrypick-robot mentioned this pull request Dec 16, 2025

[release-4.18] OCPBUGS-69395: E2E add test to verify guaranteed pod is running after kubelet restart #1448

Open

[release-4.19] OCPBUGS-59633: E2E add test to verify guaranteed pod is running after kubelet restart #1365

[release-4.19] OCPBUGS-59633: E2E add test to verify guaranteed pod is running after kubelet restart #1365

Uh oh!

Conversation

openshift-cherrypick-robot commented Jul 22, 2025

Uh oh!

openshift-ci-robot commented Jul 22, 2025

Uh oh!

openshift-ci-robot commented Jul 22, 2025

Uh oh!

mrniranjan commented Aug 7, 2025

Uh oh!

openshift-ci-robot commented Aug 7, 2025

Uh oh!

MarSik Aug 25, 2025

Choose a reason for hiding this comment

Uh oh!

mrniranjan Aug 25, 2025

Choose a reason for hiding this comment

Uh oh!

MarSik left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Aug 25, 2025

Uh oh!

MarSik commented Sep 1, 2025

Uh oh!

openshift-ci bot commented Sep 1, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Sep 1, 2025

Uh oh!

openshift-bot commented Sep 1, 2025

Uh oh!

openshift-merge-robot commented Sep 3, 2025

Uh oh!

mrniranjan commented Dec 16, 2025

Uh oh!

openshift-cherrypick-robot commented Dec 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants