Skip to content

OCPNODE-4179: Migrating test case OCP-80983 from openshift-tests-private to origin#30899

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Chandan9112:migrate-ocp-80983
Apr 1, 2026
Merged

OCPNODE-4179: Migrating test case OCP-80983 from openshift-tests-private to origin#30899
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Chandan9112:migrate-ocp-80983

Conversation

@Chandan9112
Copy link
Copy Markdown
Contributor

@Chandan9112 Chandan9112 commented Mar 18, 2026

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

Note for Reviewer:

Moved MicroShift skip check from individual test cases to g.BeforeEach block,
following the same pattern used in node_swap.go and image_volume.go.
This avoids duplicating the check inside every test case.

It passed successfully while executing on a live OCP 4.22 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983] [Suite:openshift/conformance/parallel]"

 Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
  ===================================================================
  Random Seed: 1774939031 - will randomize all specs

  Will run 1 of 1 specs
  ------------------------------
  [sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983]
  github.com/openshift/origin/test/extended/node/node_e2e/node.go:81
    STEP: Creating a kubernetes client @ 03/31/26 12:07:15.708
  I0331 12:07:15.709451   96682 discovery.go:214] Invalidating discovery information
  I0331 12:07:15.710547 96682 framework.go:2330] [precondition-check] checking if cluster is MicroShift
  I0331 12:07:16.016298 96682 framework.go:2353] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
    STEP: Check cgroup version on all Ready worker nodes @ 03/31/26 12:07:16.016
  I0331 12:07:30.469112 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-a-fk5rv: [cgroup2fs]
  I0331 12:07:42.882123 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-b-c4t77: [cgroup2fs]
  I0331 12:07:56.400872 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-c-p2bbl: [cgroup2fs]
    STEP: Changing cgroup from v2 to v1 should result in error @ 03/31/26 12:07:56.4
  I0331 12:07:58.000764 96682 client.go:1094] Error running oc --kubeconfig=/Users/cmaurya/Downloads/cluster-bot-2026-03-31-025450.kubeconfig patch nodes.config.openshift.io cluster -p {"spec": {"cgroupMode": "v1"}} --type=merge:
  StdOut>
  The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
  StdErr>
  The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

  • [42.312 seconds]
  ------------------------------

  Ran 1 of 1 Specs in 42.313 seconds
  SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

@openshift-ci-robot
Copy link
Copy Markdown

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 18, 2026
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 18, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 18, 2026

@Chandan9112: This pull request references OCPNODE-4179 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 the "4.22.0" version, but no target version was set.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • All nodes are in Ready state
  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • Kernel arguments include cgroupv2 parameters
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

It passed successfully while executing on a live OCP 4.21 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager should verify cgroupv2 is the default and cgroupv1 cannot be set [OCP-80983] [apigroup:config.openshift.io] [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
===================================================================
 Random Seed: 1773824700 - will randomize all specs
 Will run 1 of 1 specs

[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager should verify cgroupv2 is the default and cgroupv1 cannot be set [OCP-80983] [apigroup:config.openshift.io] [apigroup:machineconfiguration.openshift.io]
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:83
   STEP: Creating a kubernetes client @ 03/18/26 14:35:04.858
 I0318 14:35:04.859488   74544 discovery.go:214] Invalidating discovery information
 I0318 14:35:04.860832 74544 framework.go:2324] [precondition-check] checking if cluster is MicroShift
 I0318 14:35:05.119305 74544 framework.go:2348] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: Step 1: Checking all nodes are Ready @ 03/18/26 14:35:05.119
 I0318 14:35:10.785102 74544 node.go:105] All 6 nodes are Ready
   STEP: Step 2: Verifying cgroup version is v2 on a worker node @ 03/18/26 14:35:10.785
 I0318 14:35:13.700010 74544 node.go:118] Cgroup filesystem type on node ci-ln-1qq51kt-72292-6qbtc-worker-b-df8pw: Starting pod/ci-ln-1qq51kt-72292-6qbtc-worker-b-df8pw-debug-hrdcj ...
 To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
 cgroup2fs

 Removing debug pod ...
   STEP: Step 3: Checking kernel arguments for cgroupv2 in rendered worker MachineConfig @ 03/18/26 14:35:13.7
 I0318 14:35:14.343939 74544 node.go:127] Rendered worker MachineConfig: rendered-worker-c7db908c3514316cff8986951195a3a2
 I0318 14:35:15.185923 74544 node.go:132] Kernel arguments: systemd.unified_cgroup_hierarchy=1 cgroup_no_v1="all"
   STEP: Step 4: Verifying that setting cgroupMode to v1 is rejected by the API server @ 03/18/26 14:35:15.186
 I0318 14:35:15.715687   74544 warnings.go:110] "Warning: unknown field \"spec.minimumKubeletVersion\""
 I0318 14:35:15.716170 74544 node.go:145] cgroupMode v1 correctly rejected with error: Node.config.openshift.io "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 • [10.881 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 10.881 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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

openshift-ci bot commented Mar 18, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 18, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dcf7c586-e614-44e6-8082-740eb1eae049

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Moved MicroShift detection to a Describe-level BeforeEach that skips the entire Describe on MicroShift; removed per-test MicroShift checks. Added an It test that verifies /sys/fs/cgroup is cgroupv2 and that patching nodes.config.openshift.io/cluster.spec.cgroupMode to v1 is rejected.

Changes

Cohort / File(s) Summary
Test setup and cgroup validation
test/extended/node/node_e2e/node.go
Added a Describe-level g.BeforeEach calling exutil.IsMicroShiftCluster(...) to skip the Describe on MicroShift; removed inline MicroShift handling from the KUBELET_LOG_LEVEL test. Added [OTP] validate cgroupv2 is default It: checks /sys/fs/cgroup reports cgroup2fs and asserts a patch setting spec.cgroupMode: v1 on nodes.config.openshift.io/cluster fails with an "Unsupported value" message.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Comment thread test/extended/node/node_e2e/node.go Outdated
Comment thread test/extended/node/node_e2e/node.go Outdated
})

//author: cmaurya@redhat.com
g.It("should verify cgroupv2 is the default and cgroupv1 cannot be set [OCP-80983] [apigroup:config.openshift.io] [apigroup:machineconfiguration.openshift.io]", func() {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Add the “[OTP]” annotation in the test name to tests that are ported from openshift-test-private. And also I think no need to add Polarian test case name.
Can remove [OCP-80983] [apigroup:config.openshift.io] [apigroup:machineconfiguration.openshift.io] .

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Changed in the latest comit

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 19, 2026

@Chandan9112: This pull request references OCPNODE-4179 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 the "4.22.0" version, but no target version was set.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • All nodes are in Ready state
  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • Kernel arguments include cgroupv2 parameters
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

It passed successfully while executing on a live OCP 4.21 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager should verify cgroupv2 is the default and cgroupv1 cannot be set [OCP-80983] [apigroup:config.openshift.io] [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
===================================================================
 Random Seed: 1773824700 - will randomize all specs
 Will run 1 of 1 specs

[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] should verify cgroupv2 is the default and cgroupv1 cannot be set
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:83
   STEP: Creating a kubernetes client @ 03/19/26 13:48:59.651
 I0319 13:48:59.652863   48747 discovery.go:214] Invalidating discovery information
 I0319 13:48:59.654028 48747 framework.go:2324] [precondition-check] checking if cluster is MicroShift
 I0319 13:48:59.908333 48747 framework.go:2348] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: 1) Checking all nodes are Ready @ 03/19/26 13:48:59.908
 I0319 13:49:04.792688 48747 node.go:105] All 6 nodes are Ready
   STEP: 2) Verifying cgroup version is v2 on a worker node @ 03/19/26 13:49:04.792
 I0319 13:49:16.759908 48747 node.go:118] Cgroup filesystem type on node ci-ln-qg4f142-72292-hsbcd-worker-a-79n8q: Starting pod/ci-ln-qg4f142-72292-hsbcd-worker-a-79n8q-debug-8pqwh ...
 To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
 cgroup2fs

 Removing debug pod ...
   STEP: 3) Checking kernel arguments for cgroupv2 in rendered worker MachineConfig @ 03/19/26 13:49:16.76
 I0319 13:49:17.397260 48747 node.go:127] Rendered worker MachineConfig: rendered-worker-3eb6a567caccbdd0b82963e7c0011c54
 I0319 13:49:18.365552 48747 node.go:132] Kernel arguments: systemd.unified_cgroup_hierarchy=1 cgroup_no_v1="all"
   STEP: 4) Verifying that setting cgroupMode to v1 is rejected by the API server @ 03/19/26 13:49:18.365
 I0319 13:49:18.889681   48747 warnings.go:110] "Warning: unknown field \"spec.minimumKubeletVersion\""
 I0319 13:49:18.890194 48747 node.go:145] cgroupMode v1 correctly rejected with error: Node.config.openshift.io "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 • [19.257 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 19.258 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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
Copy Markdown

openshift-ci-robot commented Mar 19, 2026

@Chandan9112: This pull request references OCPNODE-4179 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 the "4.22.0" version, but no target version was set.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • All nodes are in Ready state
  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • Kernel arguments include cgroupv2 parameters
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

It passed successfully while executing on a live OCP 4.21 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] should verify cgroupv2 is the default and cgroupv1 cannot be set [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
===================================================================
 Random Seed: 1773824700 - will randomize all specs
 Will run 1 of 1 specs

[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] should verify cgroupv2 is the default and cgroupv1 cannot be set
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:83
   STEP: Creating a kubernetes client @ 03/19/26 13:48:59.651
 I0319 13:48:59.652863   48747 discovery.go:214] Invalidating discovery information
 I0319 13:48:59.654028 48747 framework.go:2324] [precondition-check] checking if cluster is MicroShift
 I0319 13:48:59.908333 48747 framework.go:2348] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: 1) Checking all nodes are Ready @ 03/19/26 13:48:59.908
 I0319 13:49:04.792688 48747 node.go:105] All 6 nodes are Ready
   STEP: 2) Verifying cgroup version is v2 on a worker node @ 03/19/26 13:49:04.792
 I0319 13:49:16.759908 48747 node.go:118] Cgroup filesystem type on node ci-ln-qg4f142-72292-hsbcd-worker-a-79n8q: Starting pod/ci-ln-qg4f142-72292-hsbcd-worker-a-79n8q-debug-8pqwh ...
 To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
 cgroup2fs

 Removing debug pod ...
   STEP: 3) Checking kernel arguments for cgroupv2 in rendered worker MachineConfig @ 03/19/26 13:49:16.76
 I0319 13:49:17.397260 48747 node.go:127] Rendered worker MachineConfig: rendered-worker-3eb6a567caccbdd0b82963e7c0011c54
 I0319 13:49:18.365552 48747 node.go:132] Kernel arguments: systemd.unified_cgroup_hierarchy=1 cgroup_no_v1="all"
   STEP: 4) Verifying that setting cgroupMode to v1 is rejected by the API server @ 03/19/26 13:49:18.365
 I0319 13:49:18.889681   48747 warnings.go:110] "Warning: unknown field \"spec.minimumKubeletVersion\""
 I0319 13:49:18.890194 48747 node.go:145] cgroupMode v1 correctly rejected with error: Node.config.openshift.io "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 • [19.257 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 19.258 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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.

Comment thread test/extended/node/node_e2e/node.go Outdated
nodeConfig.Spec.CgroupMode = configv1.CgroupMode("v1")
_, updateErr := oc.AdminConfigClient().ConfigV1().Nodes().Update(ctx, nodeConfig, metav1.UpdateOptions{})
o.Expect(updateErr).To(o.HaveOccurred(), "expected API server to reject cgroupMode v1, but update succeeded")
e2e.Logf("cgroupMode v1 correctly rejected with error: %v", updateErr)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

When changing cgroup from v2 to v1, in message it should show like this: error: nodes.config.openshift.io "cluster" is invalid .

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

please update the error log message

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Changed in the latest comit. The error message will look like this.
The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 19, 2026

@Chandan9112: This pull request references OCPNODE-4179 which is a valid jira issue.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • All nodes are in Ready state
  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • Kernel arguments include cgroupv2 parameters
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

It passed successfully while executing on a live OCP 4.21 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] should verify cgroupv2 is the default and cgroupv1 cannot be set [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
===================================================================
 Random Seed: 1773824700 - will randomize all specs
 Will run 1 of 1 specs

[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:80
   STEP: Creating a kubernetes client @ 03/19/26 17:36:05.278
 I0319 17:36:05.280196   60668 discovery.go:214] Invalidating discovery information
 I0319 17:36:05.281259 60668 framework.go:2324] [precondition-check] checking if cluster is MicroShift
 I0319 17:36:05.519997 60668 framework.go:2348] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: 1) Check cgroup version @ 03/19/26 17:36:05.52
 I0319 17:36:09.345400 60668 utils.go:17] cgroup version info is: [Starting pod/ci-ln-j9j0nyt-72292-ztn64-worker-a-t9wrd-debug-cxr7d ...
 To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
 cgroup2fs

 Removing debug pod ...

   STEP: 2) Changing cgroup from v2 to v1 should result in error @ 03/19/26 17:36:09.345
 I0319 17:36:10.712419 60668 client.go:1094] Error running oc --kubeconfig=/Users/cmaurya/Downloads/cluster-bot-2026-03-19-110013.kubeconfig patch nodes.config.openshift.io cluster -p {"spec": {"cgroupMode": "v1"}} --type=merge:
 StdOut>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 StdErr>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

 • [5.453 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 5.454 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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
Copy Markdown

openshift-ci-robot commented Mar 23, 2026

@Chandan9112: This pull request references OCPNODE-4179 which is a valid jira issue.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

Note for Reviewer:

Moved MicroShift skip check from individual test cases to g.BeforeEach block,
following the same pattern used in node_swap.go and image_volume.go.
This avoids duplicating the check inside every test case.

It passed successfully while executing on a live OCP 4.21 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
 ===================================================================
 Random Seed: 1774258024 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:80
   STEP: Creating a kubernetes client @ 03/23/26 14:57:07.71
 I0323 14:57:07.711243   77055 discovery.go:214] Invalidating discovery information
 I0323 14:57:07.712443 77055 framework.go:2324] [precondition-check] checking if cluster is MicroShift
 I0323 14:57:07.955519 77055 framework.go:2348] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: 1) Check cgroup version @ 03/23/26 14:57:07.955
 I0323 14:57:20.047498 77055 node.go:86] cgroup version info is: [Starting pod/ci-ln-5jd8dwt-72292-b9f7z-worker-b-th2vp-debug-4lzp8 ...
 To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
 cgroup2fs

 Removing debug pod ...]

   STEP: 2) Changing cgroup from v2 to v1 should result in error @ 03/23/26 14:57:20.047
 I0323 14:57:21.467566 77055 client.go:1094] Error running oc --kubeconfig=/Users/cmaurya/Downloads/cluster-bot-2026-03-23-082435.kubeconfig patch nodes.config.openshift.io cluster -p {"spec": {"cgroupMode": "v1"}} --type=merge:
 StdOut>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 StdErr>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

 • [13.779 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 13.779 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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.

@Chandan9112 Chandan9112 marked this pull request as ready for review March 26, 2026 04:42
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 26, 2026
@openshift-ci openshift-ci bot requested review from lyman9966 and sairameshv March 26, 2026 04:43
@openshift-ci-robot
Copy link
Copy Markdown

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

Comment thread test/extended/node/node_e2e/node.go Outdated

g "github.com/onsi/ginkgo/v2"
o "github.com/onsi/gomega"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

remove this extra line

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

removed in the latest commit

Comment thread test/extended/node/node_e2e/node.go
@openshift-trt
Copy link
Copy Markdown

openshift-trt bot commented Mar 26, 2026

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 332f7a4

  • "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]

Comment thread test/extended/node/node_e2e/node.go Outdated
Comment thread test/extended/node/node_e2e/node.go Outdated
g.By("2) Changing cgroup from v2 to v1 should result in error")
output, err := oc.AsAdmin().WithoutNamespace().Run("patch").Args("nodes.config.openshift.io", "cluster", "-p", `{"spec": {"cgroupMode": "v1"}}`, "--type=merge").Output()
o.Expect(err).Should(o.HaveOccurred())
o.Expect(strings.Contains(output, "Unsupported value: \"v1\"")).Should(o.BeTrue())
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

same as above

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done in the latest code commit

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
test/extended/node/node_e2e/node.go (1)

19-26: Cache the MicroShift probe result instead of re-running it before every test

exutil.IsMicroShiftCluster can poll for minutes; putting it in BeforeEach repeats that cost for every It and increases timeout/flakiness risk as this block grows. Compute once per Describe and reuse the result in BeforeEach.

Suggested refactor
+import "sync"
+
 var _ = g.Describe("[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager", func() {
 	var (
 		oc = exutil.NewCLIWithoutNamespace("node").AsAdmin()
+		microShiftOnce sync.Once
+		isMicroShift bool
+		microShiftErr error
 	)

 	// Skip all tests on MicroShift clusters as MachineConfig resources are not available
 	g.BeforeEach(func() {
-		isMicroShift, err := exutil.IsMicroShiftCluster(oc.AdminKubeClient())
-		o.Expect(err).NotTo(o.HaveOccurred())
+		microShiftOnce.Do(func() {
+			isMicroShift, microShiftErr = exutil.IsMicroShiftCluster(oc.AdminKubeClient())
+		})
+		o.Expect(microShiftErr).NotTo(o.HaveOccurred())
 		if isMicroShift {
 			g.Skip("Skipping test on MicroShift cluster")
 		}
 	})

As per coding guidelines, "Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/extended/node/node_e2e/node.go` around lines 19 - 26, Compute the
MicroShift probe once and reuse it: declare a Describe-scoped (or
package-scoped) variable like cachedIsMicroShift bool, run the expensive probe a
single time (e.g., in g.BeforeSuite or at the outer Describe setup) by calling
exutil.IsMicroShiftCluster(oc.AdminKubeClient()) and storing the result (and
assert err with o.Expect(err).NotTo(o.HaveOccurred())), then change the existing
g.BeforeEach block to check cachedIsMicroShift and call g.Skip("Skipping test on
MicroShift cluster") when true instead of re-invoking
exutil.IsMicroShiftCluster; keep existing references to o.Expect and g.Skip but
remove the repeated probe call.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@test/extended/node/node_e2e/node.go`:
- Around line 90-92: The assertion is too brittle by matching the full error
sentence; relax it to assert the command failed
(o.Expect(err).Should(o.HaveOccurred())) and that the output contains stable
fragments such as "spec.cgroupMode", "Unsupported value" and the rejected value
"\"v1\"" (or "v1") instead of the entire message. Locate the patch invocation
(oc.AsAdmin().WithoutNamespace().Run("patch")... ) and replace the single
o.ContainSubstring check with multiple contains assertions for those fragments
(or a single contains that concatenates stable fragments) to make the test
resilient to wording/casing changes.

---

Nitpick comments:
In `@test/extended/node/node_e2e/node.go`:
- Around line 19-26: Compute the MicroShift probe once and reuse it: declare a
Describe-scoped (or package-scoped) variable like cachedIsMicroShift bool, run
the expensive probe a single time (e.g., in g.BeforeSuite or at the outer
Describe setup) by calling exutil.IsMicroShiftCluster(oc.AdminKubeClient()) and
storing the result (and assert err with o.Expect(err).NotTo(o.HaveOccurred())),
then change the existing g.BeforeEach block to check cachedIsMicroShift and call
g.Skip("Skipping test on MicroShift cluster") when true instead of re-invoking
exutil.IsMicroShiftCluster; keep existing references to o.Expect and g.Skip but
remove the repeated probe call.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8a542e0c-a347-48eb-b629-3c7e9932b606

📥 Commits

Reviewing files that changed from the base of the PR and between c7c5091 and c2c8ffd.

📒 Files selected for processing (1)
  • test/extended/node/node_e2e/node.go

Comment thread test/extended/node/node_e2e/node.go Outdated
@openshift-ci-robot
Copy link
Copy Markdown

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-trt
Copy link
Copy Markdown

openshift-trt bot commented Mar 26, 2026

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: c2c8ffd

  • "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]

@Chandan9112
Copy link
Copy Markdown
Contributor Author

/retest

Comment thread test/extended/node/node_e2e/node.go Outdated
//author: cmaurya@redhat.com
g.It("[OTP] validate cgroupv2 is default", func() {
g.By("Get a Ready worker node and check cgroup version")
workerNode, err := oc.AsAdmin().WithoutNamespace().Run("get").Args("nodes", "-l", "node-role.kubernetes.io/worker", "-o=jsonpath={.items[0].metadata.name}").Output()
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Here you just check the first worker, if it is not Ready we can't go on checking other workers. It's better to check all the workers and skip when any worker is not Ready.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Changes done in the latest commit. Now, each line shows the cgroup version for a different worker node which are ready and skip if not Ready.

Comment thread test/extended/node/node_e2e/node.go Outdated
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 31, 2026

@Chandan9112: This pull request references OCPNODE-4179 which is a valid jira issue.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

Note for Reviewer:

Moved MicroShift skip check from individual test cases to g.BeforeEach block,
following the same pattern used in node_swap.go and image_volume.go.
This avoids duplicating the check inside every test case.

It passed successfully while executing on a live OCP 4.21 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
 ===================================================================
 Random Seed: 1774939031 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:81
   STEP: Creating a kubernetes client @ 03/31/26 12:07:15.708
 I0331 12:07:15.709451   96682 discovery.go:214] Invalidating discovery information
 I0331 12:07:15.710547 96682 framework.go:2330] [precondition-check] checking if cluster is MicroShift
 I0331 12:07:16.016298 96682 framework.go:2353] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: Check cgroup version on all Ready worker nodes @ 03/31/26 12:07:16.016
 I0331 12:07:30.469112 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-a-fk5rv: [cgroup2fs]
 I0331 12:07:42.882123 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-b-c4t77: [cgroup2fs]
 I0331 12:07:56.400872 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-c-p2bbl: [cgroup2fs]
   STEP: Changing cgroup from v2 to v1 should result in error @ 03/31/26 12:07:56.4
 I0331 12:07:58.000764 96682 client.go:1094] Error running oc --kubeconfig=/Users/cmaurya/Downloads/cluster-bot-2026-03-31-025450.kubeconfig patch nodes.config.openshift.io cluster -p {"spec": {"cgroupMode": "v1"}} --type=merge:
 StdOut>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 StdErr>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

 • [42.312 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 42.313 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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
Copy Markdown

openshift-ci-robot commented Mar 31, 2026

@Chandan9112: This pull request references OCPNODE-4179 which is a valid jira issue.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

Note for Reviewer:

Moved MicroShift skip check from individual test cases to g.BeforeEach block,
following the same pattern used in node_swap.go and image_volume.go.
This avoids duplicating the check inside every test case.

It passed successfully while executing on a live OCP 4.22 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
 ===================================================================
 Random Seed: 1774939031 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:81
   STEP: Creating a kubernetes client @ 03/31/26 12:07:15.708
 I0331 12:07:15.709451   96682 discovery.go:214] Invalidating discovery information
 I0331 12:07:15.710547 96682 framework.go:2330] [precondition-check] checking if cluster is MicroShift
 I0331 12:07:16.016298 96682 framework.go:2353] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: Check cgroup version on all Ready worker nodes @ 03/31/26 12:07:16.016
 I0331 12:07:30.469112 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-a-fk5rv: [cgroup2fs]
 I0331 12:07:42.882123 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-b-c4t77: [cgroup2fs]
 I0331 12:07:56.400872 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-c-p2bbl: [cgroup2fs]
   STEP: Changing cgroup from v2 to v1 should result in error @ 03/31/26 12:07:56.4
 I0331 12:07:58.000764 96682 client.go:1094] Error running oc --kubeconfig=/Users/cmaurya/Downloads/cluster-bot-2026-03-31-025450.kubeconfig patch nodes.config.openshift.io cluster -p {"spec": {"cgroupMode": "v1"}} --type=merge:
 StdOut>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 StdErr>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

 • [42.312 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 42.313 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 31, 2026

@Chandan9112: This pull request references OCPNODE-4179 which is a valid jira issue.

Details

In response to this:

Adds automated test case OCP-80983 migrated from openshift-tests-private. The test validates:

  • Cgroup version is v2 (cgroup2fs) on worker nodes
  • API server rejects setting cgroupMode to v1

Here is the test case link: Polarian-80983

Note for Reviewer:

Moved MicroShift skip check from individual test cases to g.BeforeEach block,
following the same pattern used in node_swap.go and image_volume.go.
This avoids duplicating the check inside every test case.

It passed successfully while executing on a live OCP 4.22 cluster:

./openshift-tests run-test "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983] [Suite:openshift/conformance/parallel]"

Running Suite:  - /Users/cmaurya/go/src/github.com/openshift/origin
 ===================================================================
 Random Seed: 1774939031 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983]
 github.com/openshift/origin/test/extended/node/node_e2e/node.go:81
   STEP: Creating a kubernetes client @ 03/31/26 12:07:15.708
 I0331 12:07:15.709451   96682 discovery.go:214] Invalidating discovery information
 I0331 12:07:15.710547 96682 framework.go:2330] [precondition-check] checking if cluster is MicroShift
 I0331 12:07:16.016298 96682 framework.go:2353] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: Check cgroup version on all Ready worker nodes @ 03/31/26 12:07:16.016
 I0331 12:07:30.469112 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-a-fk5rv: [cgroup2fs]
 I0331 12:07:42.882123 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-b-c4t77: [cgroup2fs]
 I0331 12:07:56.400872 96682 node.go:97] cgroup version on node ci-ln-skcqnmk-72292-hzp5t-worker-c-p2bbl: [cgroup2fs]
   STEP: Changing cgroup from v2 to v1 should result in error @ 03/31/26 12:07:56.4
 I0331 12:07:58.000764 96682 client.go:1094] Error running oc --kubeconfig=/Users/cmaurya/Downloads/cluster-bot-2026-03-31-025450.kubeconfig patch nodes.config.openshift.io cluster -p {"spec": {"cgroupMode": "v1"}} --type=merge:
 StdOut>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""
 StdErr>
 The Node "cluster" is invalid: spec.cgroupMode: Unsupported value: "v1": supported values: "v2", ""

 • [42.312 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 42.313 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@lyman9966
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
Copy link
Copy Markdown
Member

@sairameshv sairameshv left a comment

Choose a reason for hiding this comment

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

/hold cancel
/verified by ci

@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 Mar 31, 2026
@Chandan9112
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-trt
Copy link
Copy Markdown

openshift-trt bot commented Mar 31, 2026

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 3eb467c

  • "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983] [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]

@openshift-trt
Copy link
Copy Markdown

openshift-trt bot commented Mar 31, 2026

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 3eb467c

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn High - "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983] [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 3eb467c

  • "[sig-node] [Jira:Node/Kubelet] Kubelet, CRI-O, CPU manager [OTP] validate cgroupv2 is default [OCP-80983] [Suite:openshift/conformance/parallel]" [Total: 6, Pass: 6, Fail: 0, Flake: 0]

Copy link
Copy Markdown
Member

@sairameshv sairameshv left a comment

Choose a reason for hiding this comment

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

/verified by ci

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 1, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Chandan9112, lyman9966, sairameshv

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

@Chandan9112
Copy link
Copy Markdown
Contributor Author

/verified by @Chandan9112

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 1, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@Chandan9112: This PR has been marked as verified by @Chandan9112.

Details

In response to this:

/verified by @Chandan9112

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

openshift-ci bot commented Apr 1, 2026

@Chandan9112: 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-merge-bot openshift-merge-bot bot merged commit b039d39 into openshift:main Apr 1, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants