Automation of OCP-55033 #30460

asahay19 · 2025-11-05T13:02:59Z

This case is about checking the Kubelet log level is 2.
Here is the test case link : https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-55033

I have ran that locally and it got passed:

` ./openshift-tests run-test "[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2 [Suite:openshift/conformance/parallel]"

Running Suite: - /Users/asahay/OCP-55033/origin

Random Seed: 1762945017 - will randomize all specs

Will run 1 of 1 specs

[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2
github.com/openshift/origin/test/extended/node/node.go:15
STEP: Creating a kubernetes client @ 11/12/25 16:27:01.774
I1112 16:27:01.775613 60942 discovery.go:214] Invalidating discovery information
STEP: check Kubelet Log Level
@ 11/12/25 16:27:01.775
I1112 16:27:13.581561 60942 node_utils.go:22]
Node Names are ip-10-0-11-243.us-east-2.compute.internal ip-10-0-15-30.us-east-2.compute.internal ip-10-0-55-165.us-east-2.compute.internal ip-10-0-56-233.us-east-2.compute.internal ip-10-0-75-169.us-east-2.compute.internal ip-10-0-95-145.us-east-2.compute.internal
I1112 16:27:14.689276 60942 node_utils.go:28]
Node ip-10-0-11-243.us-east-2.compute.internal Status is True

I1112 16:27:24.692931 60942 node_utils.go:37] KUBELET_LOG_LEVEL is 2.

• [22.939 seconds]

Ran 1 of 1 Specs in 22.939 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
{
"name": "[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2 [Suite:openshift/conformance/parallel]",
"lifecycle": "blocking",
"duration": 22939,
"startTime": "2025-11-12 10:57:01.757463 UTC",
"endTime": "2025-11-12 10:57:24.697116 UTC",
"result": "passed",
"output": " STEP: Creating a kubernetes client @ 11/12/25 16:27:01.774\n STEP: check Kubelet Log Level\n @ 11/12/25 16:27:01.775\nI1112 16:27:13.581561 60942 node_utils.go:22] \nNode Names are ip-10-0-11-243.us-east-2.compute.internal ip-10-0-15-30.us-east-2.compute.internal ip-10-0-55-165.us-east-2.compute.internal ip-10-0-56-233.us-east-2.compute.internal ip-10-0-75-169.us-east-2.compute.internal ip-10-0-95-145.us-east-2.compute.internal\nI1112 16:27:14.689276 60942 node_utils.go:28] \nNode ip-10-0-11-243.us-east-2.compute.internal Status is True\n\nI1112 16:27:24.692931 60942 node_utils.go:37] KUBELET_LOG_LEVEL is 2. \n\n"
}
]`

openshift-ci · 2025-11-05T13:04:42Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: asahay19
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

OWNERS

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

openshift-trt · 2025-11-05T18:12:39Z

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: c55cf6a

Job Name	New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift	High - "[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2 [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit

New tests seen in this PR at sha: c55cf6a

"[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2 [Suite:openshift/conformance/parallel]" [Total: 6, Pass: 5, Fail: 1, Flake: 0]

ngopalak-redhat · 2025-11-12T11:41:08Z

test/extended/node/node.go

@@ -0,0 +1,19 @@
+package node


The file name can follow the convention other tests are using for example: test/extended/node/image_volume.go
I suggest test/extended/node/check_log_level.go

Actually this File have been created for all the node QE e2e test cases which will be migrating from openshift-test-private to origin. Because all the cases are not linked to a Feature. So, for any specific feature yes we can create file like that but for the cases in OTP , we need one file like this .

The origin test suite already has the ability to run test cases in parallel, that would run faster than grouping the tests. If checking the log level is one test case, it can run independently. So we may not need a common "node.go"

ngopalak-redhat · 2025-11-12T11:41:41Z

test/extended/node/node.go

+	//e2e "k8s.io/kubernetes/test/e2e/framework"
+)
+
+var _ = g.Describe("[sig-node] NODE initContainer policy,volume,readines,quota", func() {


Already using [sig-node] , so "NODE" can be removed

ngopalak-redhat · 2025-11-12T11:43:06Z

test/extended/node/node_utils.go

@@ -0,0 +1,61 @@
+package node


This can be part of the test instead of a node_utils as this is the real test.

ngopalak-redhat · 2025-11-12T11:45:55Z

test/extended/node/node_utils.go

+	e2e "k8s.io/kubernetes/test/e2e/framework"
+)
+
+func assertKubeletLogLevel(oc *exutil.CLI) {


Did the test pass on all the platforms? I think the debug pod image may not be available on all platforms

I checked on aws, gcp, arm64 and amd64 builds.

Did you check if all the tests that run as part of the PR itself passes? For example, microshift.

ngopalak-redhat · 2025-11-12T11:47:59Z

test/extended/node/OWNERS

@@ -0,0 +1,12 @@
+reviewers:


Adding reviewers could be a different PR.

No, it does in a same PR. I have updated it now.

I'm requesting this change to the OWNERS to be a different PR so that this PR focusses on the test.

openshift-trt · 2025-11-12T16:21:43Z

Job Failure Risk Analysis for sha: bc75f72

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-aws-csi	High [Monitor:pod-network-avalibility][sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=pod-to-service poller pod logs This test has passed 99.66% of 4405 runs on release 4.21 [Overall] in the last week. --- [Monitor:pod-network-avalibility][sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=host-to-service poller pod logs This test has passed 99.66% of 4405 runs on release 4.21 [Overall] in the last week. --- [Monitor:apiserver-incluster-availability][Jira: "kube-apiserver"] can collect apiserver.openshift.io/disruption-actor=poller poller pod logs This test has passed 99.98% of 4265 runs on release 4.21 [Overall] in the last week. --- [Monitor:pod-network-avalibility][sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=host-to-pod poller pod logs This test has passed 99.70% of 4405 runs on release 4.21 [Overall] in the last week. --- Showing 4 of 8 test results

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: bc75f72

Job Name	New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift	High - "[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2 [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit

New tests seen in this PR at sha: bc75f72

"[sig-node] NODE initContainer policy,volume,readines,quota check KUBELET_LOG_LEVEL is 2 [Suite:openshift/conformance/parallel]" [Total: 6, Pass: 5, Fail: 1, Flake: 0]

lyman9966 · 2025-11-17T11:53:30Z

test/extended/node/node.go

+	//e2e "k8s.io/kubernetes/test/e2e/framework"
+)
+
+var _ = g.Describe("[sig-node] NODE initContainer policy,volume,readines,quota", func() {


I think "NODE initContainer policy,volume,readines,quota" is historically-created, not precise, use "Kubelet, CRI-O, CPU manager" can be better and we can update it along with other feature cases coming in.

lyman9966 · 2025-11-17T11:55:05Z

test/extended/node/node.go

+import (
+	g "github.com/onsi/ginkgo/v2"
+	exutil "github.com/openshift/origin/test/extended/util"
+	//e2e "k8s.io/kubernetes/test/e2e/framework"


Please remove the comment if it is never used in the code

lyman9966 · 2025-11-17T12:02:51Z

test/extended/node/node_utils.go

+					return false, nil
+				}
+			} else {
+				e2e.Logf("\n NODES ARE NOT READY\n ")


Suggested change

e2e.Logf("\n NODES ARE NOT READY\n ")

e2e.Logf("\n Node %s is not Ready, Skipping\n ", node)

lyman9966 · 2025-11-17T12:34:14Z

test/extended/node/node_utils.go

+	if waitErr != nil {
+		e2e.Logf("Kubelet Log level is:\n %v\n", kubeservice)
+		e2e.Logf("Running Proccess of kubelet are:\n %v\n", kublet)
+		AssertWaitPollNoErr(waitErr, "KUBELET_LOG_LEVEL is not expected")


I think you can delete func AssertWaitPollNoErr() and replace it with:
o.Expect(waitErr).NotTo(o.HaveOccurred(), "KUBELET_LOG_LEVEL is not expected, timed out")

asahay19 · 2025-11-19T05:04:05Z

/test verify

openshift-ci · 2025-11-19T05:46:10Z

@asahay19: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-csi	`bc75f72`	link	true	`/test e2e-aws-csi`
ci/prow/e2e-aws-ovn-microshift-serial	`bc75f72`	link	true	`/test e2e-aws-ovn-microshift-serial`
ci/prow/e2e-aws-ovn-serial-1of2	`bc75f72`	link	true	`/test e2e-aws-ovn-serial-1of2`
ci/prow/e2e-aws-ovn-fips	`bc75f72`	link	true	`/test e2e-aws-ovn-fips`
ci/prow/e2e-aws-ovn-serial-2of2	`bc75f72`	link	true	`/test e2e-aws-ovn-serial-2of2`
ci/prow/e2e-gcp-ovn-upgrade	`bc75f72`	link	true	`/test e2e-gcp-ovn-upgrade`
ci/prow/e2e-gcp-ovn	`bc75f72`	link	true	`/test e2e-gcp-ovn`
ci/prow/e2e-vsphere-ovn	`bc75f72`	link	true	`/test e2e-vsphere-ovn`
ci/prow/e2e-gcp-csi	`bc75f72`	link	true	`/test e2e-gcp-csi`
ci/prow/e2e-aws-ovn-microshift	`bc75f72`	link	true	`/test e2e-aws-ovn-microshift`
ci/prow/e2e-vsphere-ovn-upi	`bc75f72`	link	true	`/test e2e-vsphere-ovn-upi`
ci/prow/verify	`2989d03`	link	true	`/test verify`
ci/prow/e2e-metal-ipi-ovn-ipv6	`2989d03`	link	true	`/test e2e-metal-ipi-ovn-ipv6`

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.

asahay19 · 2025-11-21T09:16:05Z

New PR link : http://github.com/openshift/origin/pull/30512

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 Nov 5, 2025

openshift-ci bot requested review from deads2k and p0lyn0mial November 5, 2025 13:04

openshift-ci bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Nov 5, 2025

asahay19 force-pushed the ocp55033 branch from c55cf6a to e5de674 Compare November 12, 2025 10:59

asahay19 changed the title ~~[WIP] Automation of OCP-55033~~ Automation of OCP-55033 Nov 12, 2025

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 Nov 12, 2025

ngopalak-redhat suggested changes Nov 12, 2025

View reviewed changes

ngopalak-redhat reviewed Nov 12, 2025

View reviewed changes

asahay19 force-pushed the ocp55033 branch from e5de674 to bc75f72 Compare November 12, 2025 11:52

openshift-ci bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Nov 12, 2025

lyman9966 reviewed Nov 17, 2025

View reviewed changes

Automation of OCP-55033

2989d03

asahay19 force-pushed the ocp55033 branch from bc75f72 to 2989d03 Compare November 18, 2025 11:39

asahay19 closed this by deleting the head repository Nov 20, 2025

asahay19 mentioned this pull request Nov 21, 2025

Automating OCP-55033 in Origin #30512

Open

	e2e.Logf("\n NODES ARE NOT READY\n ")
	e2e.Logf("\n Node %s is not Ready, Skipping\n ", node)

Automation of OCP-55033 #30460

Automation of OCP-55033 #30460

Uh oh!

Conversation

asahay19 commented Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Running Suite: - /Users/asahay/OCP-55033/origin

Will run 1 of 1 specs

• [22.939 seconds]

Uh oh!

openshift-ci bot commented Nov 5, 2025

Uh oh!

openshift-trt bot commented Nov 5, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-trt bot commented Nov 12, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

asahay19 commented Nov 19, 2025

Uh oh!

openshift-ci bot commented Nov 19, 2025

Uh oh!

asahay19 commented Nov 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

asahay19 commented Nov 5, 2025 •

edited

Loading