Skip to content

USHIFT-6886: Comment out tuned boot-wait in ginkgo-multi-config scenario#6570

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
agullon:USHIFT-6886-main
Apr 24, 2026
Merged

USHIFT-6886: Comment out tuned boot-wait in ginkgo-multi-config scenario#6570
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
agullon:USHIFT-6886-main

Conversation

@agullon

@agullon agullon commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Comment out the boot-wait loop in el98-lrel@ginkgo-multi-config that expects a microshift-tuned reboot
  • The scenario uses start_image=rhel98-brew-lrel-optional which has no tuned configuration, so the reboot never happens and the 60s timeout always fires
  • The tuned image blueprint is disabled because kernel-rt is unavailable on RHEL 9.8

Test plan

  • Verify el98-lrel@ginkgo-multi-config scenario passes in periodic CI (no longer times out waiting for 2 boots)
  • Verify the scenario still validates TLSv1.3, LVMS, IPv6, and ginkgo tests

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Tests
    • Updated test scenario to remove boot cycle polling during pre-test readiness verification, streamlining the initialization process for TLSv1.3 and MicroShift configuration testing.

The el98-lrel@ginkgo-multi-config scenario uses start_image=rhel98-brew-lrel-optional
which does not have microshift-tuned enabled or configured. The boot-wait loop expecting
a tuned-triggered reboot will always time out since the tuned image blueprint is disabled
due to kernel-rt unavailability on RHEL 9.8.

Comment out the boot-wait block until the tuned image is re-enabled.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

pre-commit.check-secrets: ENABLED
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 23, 2026
@openshift-ci-robot

openshift-ci-robot commented Apr 23, 2026

Copy link
Copy Markdown

@agullon: This pull request references USHIFT-6886 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 bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Comment out the boot-wait loop in el98-lrel@ginkgo-multi-config that expects a microshift-tuned reboot
  • The scenario uses start_image=rhel98-brew-lrel-optional which has no tuned configuration, so the reboot never happens and the 60s timeout always fires
  • The tuned image blueprint is disabled because kernel-rt is unavailable on RHEL 9.8

Test plan

  • Verify el98-lrel@ginkgo-multi-config scenario passes in periodic CI (no longer times out waiting for 2 boots)
  • Verify the scenario still validates TLSv1.3, LVMS, IPv6, and ginkgo tests

🤖 Generated with Claude Code

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.

@coderabbitai

coderabbitai Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

A test scenario's pre-test readiness logic was modified to skip boot-count polling verification. The 60-second polling loop is now commented out with a TODO note, allowing the test flow to proceed directly to TLSv1.3 configuration and MicroShift preparation.

Changes

Cohort / File(s) Summary
Test Scenario Boot Logic
test/scenarios/releases/el98-lrel@ginkgo-multi-config.sh
Commented out boot-count polling loop with TODO placeholder; test flow now bypasses VM/node reboot completion verification and proceeds directly to TLSv1.3 configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: commenting out a boot-wait loop in a specific test scenario file.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The pull request modifies a shell script test orchestration file without introducing or modifying any Ginkgo test name definitions.
Test Structure And Quality ✅ Passed Custom check not applicable—file is bash shell script for test orchestration, not Ginkgo test code.
Microshift Test Compatibility ✅ Passed This pull request does not add any new Ginkgo e2e tests. The change is in a shell script test scenario file that merely comments out a boot-count polling loop in the pre-test setup.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies shell script orchestrating tests, not Ginkgo test files. No new e2e test declarations added; SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed Pull request modifies test scenario shell script orchestrating test infrastructure, not deployment manifests or operator/controller code defining scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The OTE Binary Stdout Contract is not applicable to this pull request. The modified file is a shell script test scenario, not a Go binary, and falls outside the contract scope.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR modifies only a shell scenario script, not Ginkgo e2e test code. Check applies only when new Ginkgo tests are added.

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

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

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2026

@coderabbitai coderabbitai Bot left a comment

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.

🧹 Nitpick comments (1)
test/scenarios/releases/el98-lrel@ginkgo-multi-config.sh (1)

51-66: Prefer conditional gating over commented-out logic.

This change is valid for the current image, but preserving the full loop as comments is brittle. Gate the wait by start_image (or a dedicated flag) so re-enable is automatic when tuned images return.

Suggested refactor
-    # TODO: Re-enable once kernel-rt is available for RHEL 9.8 and the
-    # rhel98-brew-lrel-tuned image is used as start_image.
-    # # Wait for microshift-tuned to reboot the node
-    # local -r start_time=$(date +%s)
-    # while true; do
-    #     boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true)
-    #     boot_num="${boot_num%$'\r'*}"
-    #     if [[ "${boot_num}" -ge 2 ]]; then
-    #         break
-    #     fi
-    #     if [ $(( $(date +%s) - start_time )) -gt 60 ]; then
-    #         echo "Timed out waiting for VM having 2 boots"
-    #         exit 1
-    #     fi
-    #     sleep 5
-    # done
+    if [[ "${start_image}" == *"-tuned" ]]; then
+        # Wait for microshift-tuned to reboot the node.
+        local -r start_time=$(date +%s)
+        while true; do
+            local boot_num
+            boot_num=$(run_command_on_vm host1 "sudo journalctl --list-boots --quiet | wc -l" || true)
+            boot_num="${boot_num%$'\r'*}"
+            [[ "${boot_num}" -ge 2 ]] && break
+            if [ $(( $(date +%s) - start_time )) -gt 60 ]; then
+                echo "Timed out waiting for VM having 2 boots"
+                exit 1
+            fi
+            sleep 5
+        done
+    else
+        echo "INFO: Skipping tuned reboot wait for start_image=${start_image}"
+    fi
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/scenarios/releases/el98-lrel`@ginkgo-multi-config.sh around lines 51 -
66, Replace the commented-out reboot-wait loop with a conditional guard so the
logic runs automatically for the tuned image instead of being left as comments;
specifically, restore the loop that checks boot count via run_command_on_vm and
the timeout logic but wrap it in a conditional on start_image (e.g. test for
"rhel98-brew-lrel-tuned") or a new boolean flag (e.g. WAIT_FOR_TUNED_REBOOT) and
execute the loop only when that condition is true; keep the loop body and
timeout behavior intact and remove the commented block.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@test/scenarios/releases/el98-lrel`@ginkgo-multi-config.sh:
- Around line 51-66: Replace the commented-out reboot-wait loop with a
conditional guard so the logic runs automatically for the tuned image instead of
being left as comments; specifically, restore the loop that checks boot count
via run_command_on_vm and the timeout logic but wrap it in a conditional on
start_image (e.g. test for "rhel98-brew-lrel-tuned") or a new boolean flag (e.g.
WAIT_FOR_TUNED_REBOOT) and execute the loop only when that condition is true;
keep the loop body and timeout behavior intact and remove the commented block.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 73493424-a1af-4119-8b08-cc41789d1c8a

📥 Commits

Reviewing files that changed from the base of the PR and between 7ae3864 and e7bdb37.

📒 Files selected for processing (1)
  • test/scenarios/releases/el98-lrel@ginkgo-multi-config.sh

@ggiguash

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 23, 2026
@openshift-ci

openshift-ci Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

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

@agullon

agullon commented Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@agullon

agullon commented Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

/verified by CI

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

Copy link
Copy Markdown

@agullon: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@agullon

agullon commented Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

/cherrypick release-4.22

@openshift-cherrypick-robot

Copy link
Copy Markdown

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

Details

In response to this:

/cherrypick release-4.22

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-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 87caff2 and 2 for PR HEAD e7bdb37 in total

@agullon

agullon commented Apr 24, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci

openshift-ci Bot commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

@agullon: 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 1320339 into openshift:main Apr 24, 2026
19 checks passed
@openshift-cherrypick-robot

Copy link
Copy Markdown

@agullon: new pull request created: #6577

Details

In response to this:

/cherrypick release-4.22

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.

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.

4 participants