Skip to content

OCPNODE-4494: e2e test case for RHCOS upgrade from 9 → 10#31393

Open
asahay19 wants to merge 1 commit into
openshift:mainfrom
asahay19:rhcos-upgrade
Open

OCPNODE-4494: e2e test case for RHCOS upgrade from 9 → 10#31393
asahay19 wants to merge 1 commit into
openshift:mainfrom
asahay19:rhcos-upgrade

Conversation

@asahay19

@asahay19 asahay19 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds the crun happy-path e2e test for RHCOS 9 → 10 osImageStream upgrades, complementing the runc guard test merged in #31266 (UC6A).
On OCP 5.0–5.2 clusters with dual OS streams and crun as the default runtime, moving a pool from rhel-9 to rhel-10 should succeed without triggering the runc-on-RHCOS-10 guard. This test validates that recommended upgrade path.

What the test does

  1. Creates an isolated MachineConfigPool pinned to rhel-9 (no runc ContainerRuntimeConfig)
  2. Labels one pure worker into the pool and waits for rollout on RHCOS 9 with crun
  3. Patches the pool to rhel-10
  4. Asserts:
    • MCP reaches ready without RenderDegraded / Degraded
    • Node reboots to RHCOS 10 and stays Ready
    • Runtime remains crun (no runc CRI-O drop-in)
    • co/machine-config is not Upgradeable=False (reason DegradedPool)

Changes

  • test/extended/node/runc_upgrade_cases.go — new It + helpers; shared AfterEach parameterized by pool name

  • test/extended/node/runc_upgrade_cases.md — documents both UC6A and UC5/UC14

  • Epic: OCPNODE-4013

Locally executed on Openshift cluster 5.0, it got executed successfully:

./openshift-tests run-test \
  "[Suite:openshift/disruptive-longrunning][sig-node][Serial][Disruptive][OCPFeatureGate:OSStreams] runc RHCOS 10 upgrade guard allows RHCOS 9 to 10 osImageStream upgrade when default runtime is crun"
  
    ------------------------------

  Ran 1 of 1 Specs in 506.229 seconds
  SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
  {
    "name": "[Suite:openshift/disruptive-longrunning][sig-node][Serial][Disruptive][OCPFeatureGate:OSStreams] runc RHCOS 10 upgrade guard allows RHCOS 9 to 10 osImageStream upgrade when default runtime is crun",
    "lifecycle": "informing",
    "duration": 506253,
    "startTime": "2026-07-15 12:13:34.449119 UTC",
    "endTime": "2026-07-15 12:22:00.702706 UTC",
    "result": "passed",

Summary by CodeRabbit

  • Tests

    • Expanded OS image upgrade end-to-end coverage with an inverse runc-guard scenario for nodes whose default runtime is crun (RHCOS 9→10).
    • Added a crun happy-path upgrade case that validates pinned MCP behavior, successful upgrade to rhel-10, node reboot onto the target OS image, and post-upgrade health checks (including that cluster upgradeability is not blocked by the isolated degraded-pool reason).
    • Improved runtime validation using polling/retry-style checks for more reliable readiness verification.
  • Documentation

    • Updated the RHCOS 9→10 upgrade test case documentation with clearer UC6A vs UC5/UC14 expectations, timing guidance, and notes explaining RenderDegraded versus delayed Degraded behavior and supported runtime configuration.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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 Jul 16, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 16, 2026

Copy link
Copy Markdown

@asahay19: This pull request references OCPNODE-4494 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 "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Adds the crun happy-path e2e test for RHCOS 9 → 10 osImageStream upgrades, complementing the runc guard test merged in #31266 (UC6A).
On OCP 5.0–5.2 clusters with dual OS streams and crun as the default runtime, moving a pool from rhel-9 to rhel-10 should succeed without triggering the runc-on-RHCOS-10 guard. This test validates that recommended upgrade path.

What the test does

  1. Creates an isolated MachineConfigPool pinned to rhel-9 (no runc ContainerRuntimeConfig)
  2. Labels one pure worker into the pool and waits for rollout on RHCOS 9 with crun
  3. Patches the pool to rhel-10
  4. Asserts:
  • MCP reaches ready without RenderDegraded / Degraded
  • Node reboots to RHCOS 10 and stays Ready
  • Runtime remains crun (no runc CRI-O drop-in)
  • co/machine-config is not Upgradeable=False (reason DegradedPool)

Changes

  • test/extended/node/runc_upgrade_cases.go — new It + helpers; shared AfterEach parameterized by pool name

  • test/extended/node/runc_upgrade_cases.md — documents both UC6A and UC5/UC14

  • Epic: OCPNODE-4013

Locally executed on Openshift cluster 5.0, it got executed successfully:

./openshift-tests run-test \
 "[Suite:openshift/disruptive-longrunning][sig-node][Serial][Disruptive][OCPFeatureGate:OSStreams] runc RHCOS 10 upgrade guard allows RHCOS 9 to 10 osImageStream upgrade when default runtime is crun"
 
   ------------------------------

 Ran 1 of 1 Specs in 506.229 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Suite:openshift/disruptive-longrunning][sig-node][Serial][Disruptive][OCPFeatureGate:OSStreams] runc RHCOS 10 upgrade guard allows RHCOS 9 to 10 osImageStream upgrade when default runtime is crun",
   "lifecycle": "informing",
   "duration": 506253,
   "startTime": "2026-07-15 12:13:34.449119 UTC",
   "endTime": "2026-07-15 12:22:00.702706 UTC",
   "result": "passed",

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 requested review from bitoku and sairameshv July 16, 2026 05:29
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

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

The upgrade test suite now covers runc guard behavior and the crun happy path for RHCOS 9-to-10 upgrades. Cleanup is parameterized by the active test pool, runtime checks use polling helpers, and documentation describes both scenarios and health assertions.

Changes

Runtime upgrade test coverage

Layer / File(s) Summary
Runtime scenarios and pool lifecycle
test/extended/node/runc_upgrade_cases.go
Adds the crun upgrade scenario, shared RHEL 9 pool construction, pool health checks, upgradeability validation, and parameterized cleanup.
Runtime polling and readiness helpers
test/extended/node/runc_upgrade_cases.go
Separates polling helpers for runc and crun runtime checks from immediate node readiness assertions, including transient debug-unavailable handling.
Upgrade case documentation
test/extended/node/runc_upgrade_cases.md
Documents the runc guard and crun happy-path cases, commands, condition timing, runtime estimates, and runtime configuration details.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant UpgradeTest
  participant MachineConfigPool
  participant WorkerNode
  participant ClusterOperator
  UpgradeTest->>MachineConfigPool: Create rhel-9 runtime-specific pool
  UpgradeTest->>WorkerNode: Apply pool label and verify runtime
  UpgradeTest->>MachineConfigPool: Set osImageStream to rhel-10
  MachineConfigPool->>WorkerNode: Roll out upgraded configuration
  UpgradeTest->>MachineConfigPool: Assert pool is not RenderDegraded
  UpgradeTest->>ClusterOperator: Check DegradedPool does not block upgradeability
Loading

Suggested reviewers: sairameshv


Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

  • Ignore

❌ Failed checks (1 error)

Check name Status Explanation Resolution
No-Sensitive-Data-In-Logs ❌ Error New logs print nodeName and related identifiers in cleanup/rollout helpers, which can expose internal hostnames in CI logs. Remove or redact node/host identifiers from logs, or gate them behind debug-only output with sanitized IDs.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: adding an end-to-end test for RHCOS 9→10 upgrade behavior.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 Both new Ginkgo It names are static literals; no runtime/node/pod/UUID/date interpolation or generated identifiers were introduced.
Test Structure And Quality ✅ Passed Two focused It blocks with AfterEach cleanup; all cluster waits use explicit timeouts, and key assertions include diagnostic messages, matching repo style.
Microshift Test Compatibility ✅ Passed PASS: the new It()s are under a Describe whose BeforeEach calls exutil.IsMicroShiftCluster() and g.Skip() on MicroShift.
Single Node Openshift (Sno) Test Compatibility ✅ Passed BeforeEach skips SingleReplicaTopology, so the new crun test is already protected from SNO despite needing a pure worker.
Topology-Aware Scheduling Compatibility ✅ Passed Only e2e test/doc changes; no deployment/operator scheduling logic. The test skips SNO/HyperShift and labels a worker, not workloads.
Ote Binary Stdout Contract ✅ Passed No process-level stdout writes found; the changed Go file has no fmt.Print/log/klog stdout usage, and its logging is confined to AfterEach cleanup.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed New Ginkgo tests use only cluster APIs/node debug; no hardcoded IPv4, IP parsing, or public internet connectivity was found.
No-Weak-Crypto ✅ Passed Changed files are only node e2e test/docs; scans found no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons.
Container-Privileges ✅ Passed Only test Go/MD files changed; no container/K8s manifests or privileged settings were added, and the MCP/CRC builders lack securityContext flags.
✨ 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.

@openshift-ci openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Jul 16, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@bitoku bitoku 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.

overall lgtm,
One comment about the style.
There's some functions like assert*, wait*, expect*, verify*.
I don't mind either, but want them to be consistent or follow a rule (for example, expect calls Expect in the function, something like that).

Comment on lines +62 to +64
nodeName = ""
testPoolName = ""
cleanupCRC = false

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.

nit: I don't think they are needed. They should be initialized when it's defined.

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.

Dropped redundant BeforeEach resets for nodeName / testPoolName / cleanupCRC in the latest commit


g.By("Upgrading RHCOS version to RHCOS 10 via osImageStream")
o.Expect(setPoolOSImageStream(ctx, mcClient, crunRHCOS10UpgradePool, streamRHEL10)).To(o.Succeed())
o.Expect(waitForMCP(ctx, mcClient, crunRHCOS10UpgradePool, 45*time.Minute)).To(o.Succeed(),

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.

nit: I think 45 mins is too long. It's supposed to be finished much earlier.

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.

Reduced post-rhel-10 MCP and node waits from 45m to 30m

"pool should roll out to rhel-10 without runc guard RenderDegraded")

g.By("Verifying node rolled out to RHCOS 10 with crun and pool stayed healthy")
o.Expect(waitForNodeRHELMajorVersion(ctx, oc, nodeName, "10", 45*time.Minute)).To(o.Succeed(),

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.

nit: I think 45 mins is too long. It's supposed to be finished much earlier.

if upgradeable != nil &&
upgradeable.Status == configv1.ConditionFalse &&
upgradeable.Reason == degradedPoolUpgradeableReason {
return fmt.Errorf("ClusterOperator %s Upgradeable=False (reason %s) after crun rhel-10 upgrade: %q",

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.

Too specific error message, this may be confusing in the future when someone uses this function.

Suggested change
return fmt.Errorf("ClusterOperator %s Upgradeable=False (reason %s) after crun rhel-10 upgrade: %q",
return fmt.Errorf("ClusterOperator %s Upgradeable=False (reason %s): %q",

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.

Generalized assertMachineConfigNotBlockedByDegradedPool error message in the latest commit

@bitoku

bitoku commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2 periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2
  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/07d107d0-8112-11f1-980f-e0e7979d9599-0

@asahay19
asahay19 force-pushed the rhcos-upgrade branch 2 times, most recently from dfe3764 to c6aab91 Compare July 17, 2026 11:42
@asahay19

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bc3277f0-81d4-11f1-91a5-e78e2058153d-0

@asahay19

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/cab5adb0-81d4-11f1-9135-6cfa88222756-0

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@asahay19

Copy link
Copy Markdown
Contributor Author

/retest

1 similar comment
@asahay19

Copy link
Copy Markdown
Contributor Author

/retest

@asahay19

Copy link
Copy Markdown
Contributor Author

/retest

Comment on lines +731 to +750
func waitForCrunRuntimeOnNode(ctx context.Context, oc *exutil.CLI, nodeName string, timeout time.Duration) error {
err := wait.PollUntilContextTimeout(ctx, 10*time.Second, timeout, true, func(ctx context.Context) (bool, error) {
err := assertCrunRuntimeOnNode(ctx, oc, nodeName)
if err != nil {
if strings.Contains(err.Error(), "debug unavailable") {
framework.Logf("Transient debug error checking crun on node %s: %v", nodeName, err)
return false, nil
}
return false, err
}
return true, nil
})
if err != nil {
if wait.Interrupted(err) {
return fmt.Errorf("node %s does not have crun as default runtime within %s", nodeName, timeout)
}
return err
}
return nil
}

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.

Comment from Claude. Please check it.

  1. waitForCrunRuntimeOnNode doesn't actually wait — The function wraps assertCrunRuntimeOnNode in a poll loop, but assertCrunRuntimeOnNode returns an error (not a bool) when runc is still present. The poll treats this as a permanent failure and aborts immediately instead of retrying.
    Compare with waitForRuncRuntimeOnNode which correctly calls hasRuncRuntimeOnNode directly and returns (false, nil) to keep polling. Fix: call hasRuncRuntimeOnNode directly and invert the logic, matching the sibling pattern.

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.

Fixed waitForCrunRuntimeOnNode to poll via hasCrunRuntimeOnNode (same pattern as waitForRuncRuntimeOnNode) in the latest commit

clusterDefaultStream string
)

g.BeforeEach(func(ctx context.Context) {

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.

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.

Restored BeforeEach resets for nodeName / testPoolName / cleanup

Comment on lines +941 to +947
mcp := &machineconfigv1.MachineConfigPool{
ObjectMeta: metav1.ObjectMeta{
Name: crunRHCOS10UpgradePool,
Labels: map[string]string{
poolOperatorLabel(crunRHCOS10UpgradePool): "",
},
},

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.

nit: I guess we can reuse createRuncUpgradeMCP?

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.

Deduplicated MCP creation into createRHEL9UpgradeMCP, reused by both guard and crun paths

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

clusterDefaultStream string
)

g.BeforeEach(func(ctx context.Context) {

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.

@bitoku

bitoku commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@@ -807,17 +872,16 @@ func waitForNodeRHELMajorVersion(ctx context.Context, oc *exutil.CLI, nodeName,
}

func assertCrunRuntimeOnNode(ctx context.Context, oc *exutil.CLI, nodeName string) error {

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.

Can this be removed?

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.

This is not used anymore.

@bitoku

bitoku commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2 periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2
  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f4665d40-8516-11f1-874e-f8074f7d5322-0

@asahay19

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

@asahay19

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ba9ac310-8518-11f1-8407-ff29209175a6-0

@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c827d900-8518-11f1-82a8-f93ef54c43b1-0

@Chandan9112

Copy link
Copy Markdown
Contributor

/retest

1 similar comment
@asahay19

Copy link
Copy Markdown
Contributor Author

/retest

@asahay19

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

@asahay19

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/983e8b40-85d5-11f1-8ede-0260f2967932-0

@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a1470370-85d5-11f1-9f40-5a94e5ca5011-0

@bitoku bitoku 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.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@asahay19

Copy link
Copy Markdown
Contributor Author

/verified by @asahay19
Ran the payload jobs and both of it got passed.

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

Copy link
Copy Markdown

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

Details

In response to this:

/verified by @asahay19
Ran the payload jobs and both of it got passed.

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.

@cpmeadors

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asahay19, bitoku, cpmeadors

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 Jul 23, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD c73a0bb and 2 for PR HEAD 647c28e in total

@Chandan9112

Copy link
Copy Markdown
Contributor

/retest

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 398edca and 1 for PR HEAD 647c28e in total

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@asahay19: The following test 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/verify 647c28e link unknown /test verify

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. 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. ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants