Skip to content

DNM Debug#1472

Draft
jmencak wants to merge 2 commits intoopenshift:mainfrom
jmencak:4.22-dnm-debug
Draft

DNM Debug#1472
jmencak wants to merge 2 commits intoopenshift:mainfrom
jmencak:4.22-dnm-debug

Conversation

@jmencak
Copy link
Copy Markdown
Contributor

@jmencak jmencak commented Feb 16, 2026

/cc

Summary by CodeRabbit

  • Documentation

    • Minor formatting update to the README title.
  • Tests

    • Added an early validation step to an existing test.

@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 Feb 16, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 16, 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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 16, 2026

@jmencak: GitHub didn't allow me to request PR reviews from the following users: jmencak.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc

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

openshift-ci Bot commented Feb 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 16, 2026
@jmencak
Copy link
Copy Markdown
Contributor Author

jmencak commented Apr 8, 2026

/agentic_describe

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Add trailing whitespace to README title

📦 Other

Grey Divider

Walkthroughs

Description
• Trailing whitespace added to README title

Grey Divider

File Changes

1. README.md Formatting +1/-1

Trailing whitespace modification

• Added trailing whitespace to the main title line

README.md


Grey Divider

Qodo Logo

@jmencak
Copy link
Copy Markdown
Contributor Author

jmencak commented Apr 9, 2026

/test e2e-hypershift-pao

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented Apr 9, 2026

Unsupported PR languages

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 14, 2026

Walkthrough

Minor updates to documentation and test files: README title spacing adjustment and addition of an early error assertion in the OCP-37415 Ginkgo test.

Changes

Cohort / File(s) Summary
Documentation
README.md
Added trailing space to top-level heading.
Tests
test/extended/nto.go
Added early assertion at start of OCP-37415 test to verify non-nil error condition before subsequent operations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 7 | ❌ 3

❌ Failed checks (2 warnings, 1 inconclusive)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning Test code violates multiple quality requirements including single responsibility, missing assertion messages, and inadequate timeout handling for cluster operations. Remove intentional failure assertion, add meaningful messages to all 16 assertions, and wrap cluster operations in Eventually blocks with appropriate timeouts.
Microshift Test Compatibility ⚠️ Warning Test OCP-37415 uses MachineSet API (machine.openshift.io) via ChoseOneWorkerNodeToRunCase utility without MicroShift protection mechanisms. Add [apigroup:machine.openshift.io] tag to test name or guard with exutil.IsMicroShiftCluster() check to skip on MicroShift.
Title check ❓ Inconclusive The title 'DNM Debug' is vague and does not clearly describe the specific changes in the pull request, which include a trailing space in README.md and an early debug assertion in a test file. Provide a more descriptive title that clearly indicates the main purpose of the changes, such as 'Add debug assertion to OCP-37415 test' or 'Debug OCP-37415 test with early error check'.
✅ Passed checks (7 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed The Ginkgo test name is stable and deterministic with no dynamic values embedded in the test title.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The test OCP-37415 includes proper SNO detection via utils.IsSNOCluster(oc) and conditionally selects appropriate nodes. All operations are contained to a single node and do not assume multi-node topology.
Topology-Aware Scheduling Compatibility ✅ Passed PR contains only cosmetic changes (trailing space in README) and debug test assertion; no scheduling constraints, affinity rules, topology spread constraints, or replica configurations introduced that would affect SNO, TNF, TNA, or HyperShift topologies.
Ote Binary Stdout Contract ✅ Passed The added assertion is within a Ginkgo It() test block, not at process-level code. No process-level stdout writes or logging calls were found that would violate the OTE Binary Stdout Contract.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Test modifications do not introduce IPv4 assumptions, hardcoded addresses, or external connectivity requirements. Operations use only cluster-internal APIs and proc file reads.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

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

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.4)

level=error msg="Running error: context loading failed: failed to load packages: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: go: inconsistent vendoring in :\n\tgithub.com/RHsyseng/operator-utils@v1.4.13: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt\n\tgithub.com/coreos/go-systemd@v0.0.0-20191104093116-d3cd4ed1dbcf: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt\n\tgithub.com/coreos/ignition@v0.35.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt\n\tgithub.com/coreos/ignition/v2@v2.24.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt\n\tgithub.com/docker/go-units@v0.5.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt\n\tgithub.com/go-logr/stdr@v1.2.2: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt\n\tgithub.com/google/go-cmp@v0.7.0

... [truncated 19170 characters] ...

is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\tk8s.io/legacy-cloud-providers: is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\tk8s.io/metrics: is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\tk8s.io/mount-utils: is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\tk8s.io/pod-security-admission: is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\tk8s.io/sample-apiserver: is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\tgithub.com/onsi/ginkgo/v2: is replaced in go.mod, but not marked as replaced in vendor/modules.txt\n\n\tTo ignore the vendor directory, use -mod=readonly or -mod=mod.\n\tTo sync the vendor directory, run:\n\t\tgo mod vendor\n"


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

@jmencak
Copy link
Copy Markdown
Contributor Author

jmencak commented Apr 14, 2026

/test all

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented Apr 14, 2026

PR-Agent: could not fine a component named all in a supported language in this PR.

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)
README.md (1)

1-1: Remove trailing whitespace in the top-level heading.

Line 1 has an extra trailing space after Operator; please remove it to avoid markdown lint/style noise.

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

In `@README.md` at line 1, The top-level Markdown heading "Node Tuning Operator "
contains a trailing space; remove the extra whitespace so the heading is exactly
"Node Tuning Operator" (update the README.md heading line to eliminate the
trailing space).
🤖 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/nto.go`:
- Around line 39-41: Remove the intentional failing assertion and fix the
shadowed error variable: eliminate the g.By("fail intentionally...") and the
o.Expect(err).To(o.HaveOccurred()) assertion, and ensure the test uses the
package-level or outer-scoped err (do not redeclare err with := inside
BeforeEach); if you need to assert an actual error, assign to the existing err
variable (use =) and assert its value appropriately in the test instead of
forcing a failure.

---

Nitpick comments:
In `@README.md`:
- Line 1: The top-level Markdown heading "Node Tuning Operator " contains a
trailing space; remove the extra whitespace so the heading is exactly "Node
Tuning Operator" (update the README.md heading line to eliminate the trailing
space).
🪄 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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: aa5a4f78-2105-47f6-9642-d0a92e33fd75

📥 Commits

Reviewing files that changed from the base of the PR and between f5fe446 and 5d9beec.

📒 Files selected for processing (2)
  • README.md
  • test/extended/nto.go

Comment thread test/extended/nto.go
Comment on lines +39 to +41
g.By("fail intentionally for debugging in the CI to see if the tests are actually running")
o.Expect(err).To(o.HaveOccurred())

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Intentional test failure — must not be merged.

This debugging code will always fail: err is nil at this point because it's zero-initialized on line 24, and BeforeEach shadows it with a local variable (:= on line 31). The o.Expect(err).To(o.HaveOccurred()) assertion expects a non-nil error, so the test fails as intended.

Given the PR is marked as DNM/Draft with commit message "Fail intentionally", this appears to serve its purpose for CI debugging. Ensure this is removed before any real merge.

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

In `@test/extended/nto.go` around lines 39 - 41, Remove the intentional failing
assertion and fix the shadowed error variable: eliminate the g.By("fail
intentionally...") and the o.Expect(err).To(o.HaveOccurred()) assertion, and
ensure the test uses the package-level or outer-scoped err (do not redeclare err
with := inside BeforeEach); if you need to assert an actual error, assign to the
existing err variable (use =) and assert its value appropriately in the test
instead of forcing a failure.

@jmencak
Copy link
Copy Markdown
Contributor Author

jmencak commented Apr 14, 2026

/payload-job-with-prs periodic-ci-openshift-cluster-node-tuning-operator-main-e2e-aws openshift/origin#30598

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@jmencak: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

@jmencak
Copy link
Copy Markdown
Contributor Author

jmencak commented Apr 14, 2026

/payload-job pull-ci-openshift-cluster-node-tuning-operator-main-e2e-aws-operator

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@jmencak: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

@jmencak
Copy link
Copy Markdown
Contributor Author

jmencak commented Apr 14, 2026

/payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-single-node-serial

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@jmencak: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@jmencak: 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-hypershift-pao 5d9beec link true /test e2e-hypershift-pao
ci/prow/e2e-aws-ovn-techpreview 5d9beec link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn 5d9beec link true /test e2e-aws-ovn

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.

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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant