Skip to content

CNF-16772, CNF-16780, CNF-19588, CNF-25274: Sync from upstream (08-Jul-2026)#711

Merged
openshift-merge-bot[bot] merged 10 commits into
openshift:mainfrom
jzding:upstream-sync-2026-07-08
Jul 15, 2026
Merged

CNF-16772, CNF-16780, CNF-19588, CNF-25274: Sync from upstream (08-Jul-2026)#711
openshift-merge-bot[bot] merged 10 commits into
openshift:mainfrom
jzding:upstream-sync-2026-07-08

Conversation

@jzding

@jzding jzding commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Upstream PRs included

  • #267 chore(deps): bump golang.org/x/net from 0.49.0 to 0.55.0
  • #266 CNF-25274: Add minKubeVersion to CSV for OCP 5.0 certification (CNF-25274)
  • #263 CNF-16772: Add CI tests for GM metric cleanup on PtpConfig deletion (CNF-16772,OCPBUGS-7808,OCPBUGS-7811)
  • #251 PTP CI: verify PTP processes restart and socket cleanup after termination (CNF-16780,OCPBUGS-8112)
  • #171 CNF-19588: CI test for clockClass recovery after cloud-event-proxy crash (CNF-19588)

Summary by CodeRabbit

  • New Features

    • Added support for a minimum Kubernetes version requirement in the operator metadata.
    • Improved event handling to better validate current state after disruptions and support multiple initial event topics.
    • Added readiness checks for consumer workloads before event validation begins.
  • Bug Fixes

    • Strengthened conformance coverage for restarts, proxy recovery, and config deletion/reapply scenarios.
    • Improved restart-state tracking to better detect issues during process recovery.
  • Chores

    • Updated metadata timestamps and refreshed dependency versions.

yaronh12 and others added 10 commits June 28, 2026 13:12
Addresses CNF-16772.

- Verify ts2phc clock state metric is removed after GM PtpConfig
  deletion (OCPBUGS-7808)
- Verify ts2phc config name is preserved and restart count remains
  consistent after GM PtpConfig delete/re-apply (OCPBUGS-7811)
- Add helper functions for parsing PTP metrics
…ts-coverage

CNF-16772: Add CI tests for GM metric cleanup on PtpConfig deletion
…et-and-processes

PTP CI: verify PTP processes restart and socket cleanup after termination
Set minKubeVersion: 1.35.0 to match the K8s API version (v0.35.2)
used by OCP 4.22 and 5.0, ensuring the operator only installs on
compatible clusters.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.49.0 to 0.55.0.
- [Commits](golang/net@v0.49.0...v0.55.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-version: 0.55.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Add an e2e test that verifies clock class metrics are correctly
recovered via the Event API after the cloud-event-proxy process
is killed and restarted.

Test flow:
1. Deploy consumer app and verify initial clockClass via metrics,
   PMC, and Event API
2. Kill the cloud-event-proxy process using /proc/PID/comm matching
   (portable across minimal container images without pgrep/pkill)
3. Wait for recovery via health endpoint (handles both container
   restart in Kind and process-level restart in OCP hostPID pods)
4. Verify clockClass is preserved after restart

Also includes:
- WaitForCloudEventProxyReady helper that detects container restart
  via K8s API and verifies health endpoint recovery
- WaitForConsumerReady with publisher health polling
- verifyClockClassCurrentState using fresh subscription with
  pushInitial=true (safe after disruptions)
- PushInitialEvent with context timeout to avoid hanging on
  scanner.Scan()
- Fix v2 API validation test: use health endpoint check instead
  of unreliable log search (GetPodLogsRegex with Follow times out
  on large logs in multi-node Kind clusters)
- Fix publisher readiness check: use explicit boolean flag instead
  of racy time.Now() post-loop comparison

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
CNF-19588: CI test for clockClass recovery after cloud-event-proxy crash
…/go_modules/golang.org/x/net-0.55.0

chore(deps): bump golang.org/x/net from 0.49.0 to 0.55.0
CNF-25274: Add minKubeVersion to CSV for OCP 5.0 certification
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 8, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jzding: This pull request references CNF-16772 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.

This pull request references CNF-16780 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.

This pull request references CNF-19588 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.

This pull request references CNF-25274 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.

This pull request references Jira Issue OCPBUGS-7808, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.13.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-7811, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.13.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-8112, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.14.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done-Errata) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Upstream PRs included

  • #267 chore(deps): bump golang.org/x/net from 0.49.0 to 0.55.0
  • #266 CNF-25274: Add minKubeVersion to CSV for OCP 5.0 certification (CNF-25274)
  • #263 CNF-16772: Add CI tests for GM metric cleanup on PtpConfig deletion (CNF-16772,OCPBUGS-7808,OCPBUGS-7811)
  • #251 PTP CI: verify PTP processes restart and socket cleanup after termination (CNF-16780,OCPBUGS-8112)
  • #171 CNF-19588: CI test for clockClass recovery after cloud-event-proxy crash (CNF-19588)

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

openshift-ci-robot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jzding: This pull request references CNF-16772 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.

This pull request references CNF-16780 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.

This pull request references CNF-19588 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.

This pull request references CNF-25274 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.

This pull request references Jira Issue OCPBUGS-7808, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.13.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-7811, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.13.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-8112, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.14.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done-Errata) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Upstream PRs included

  • #267 chore(deps): bump golang.org/x/net from 0.49.0 to 0.55.0
  • #266 CNF-25274: Add minKubeVersion to CSV for OCP 5.0 certification (CNF-25274)
  • #263 CNF-16772: Add CI tests for GM metric cleanup on PtpConfig deletion (CNF-16772,OCPBUGS-7808,OCPBUGS-7811)
  • #251 PTP CI: verify PTP processes restart and socket cleanup after termination (CNF-16780,OCPBUGS-8112)
  • #171 CNF-19588: CI test for clockClass recovery after cloud-event-proxy crash (CNF-19588)

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 lack and vitus133 July 8, 2026 13:43
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 8, 2026
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Walkthrough

This PR adds minKubeVersion: 1.35.0 to ClusterServiceVersion manifests and refreshes CSV timestamps, bumps several golang.org/x/* dependencies, and expands PTP conformance tests with new event-readiness helpers, health-check verification, restart/socket-error checks, and GM PtpConfig deletion behavior tests, plus a metrics constant and a log message tweak.

Changes

CSV Manifest and Dependency Updates

Layer / File(s) Summary
Add minKubeVersion and refresh CSV timestamps
bundle/manifests/ptp-operator.clusterserviceversion.yaml, config/manifests/bases/ptp-operator.clusterserviceversion.yaml, manifests/stable/ptp-operator.clusterserviceversion.yaml
Adds spec.minKubeVersion: 1.35.0 across CSV manifests and updates createdAt timestamps in bundle and stable manifests.
Bump golang.org/x/ dependency versions*
go.mod
Updates versions for x/crypto, x/mod, x/net, x/sync, x/sys, x/term, x/text, and x/tools; x/oauth2 and x/time unchanged.

PTP Conformance Test Enhancements

Layer / File(s) Summary
Consumer readiness and initial event publishing helpers
test/pkg/event/event.go
Adds WaitForConsumerReady, WaitForCloudEventProxyReady, refactors PushInitialEvent into multi-topic PushInitialEvents, changes createStoredEvent keying to prefer Resource over DataType, and updates SubscribeToGMChangeEvents to call PushInitialEvents once.
Add process restart count metric constant
test/pkg/metrics/metrics.go
Adds exported OpenshiftPtpProcessRestartCount constant.
ClockClass recovery test after cloud-event-proxy crash
test/conformance/serial/ptp.go
Adds a test validating clockClass before/after killing the cloud-event-proxy sidecar, adds verifyClockClassCurrentState, and wires consumer readiness via WaitForConsumerReady.
Event API v2 health endpoint verification
test/conformance/serial/ptp.go
Changes default and explicit apiVersion=2.0 tests to curl /health on all pods and assert "OK" instead of log matching.
SIGTERM restart and GM PtpConfig deletion tests
test/conformance/serial/ptp.go
Adds SIGTERM restart tests for ptp4l, phc2sys, ts2phc; adds ts2phc metric cleanup/re-apply tests on GM PtpConfig deletion; introduces ensureGMPtpConfigRestored, getProcessConfigAndRestartCount, and verifyProcessRestartNoSocketErrors helpers.
Adjust version comparison log message
test/pkg/ptphelper/ptphelper.go
Updates logged comparison operator from <= to < in IsPTPOperatorVersionAtLeast.

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

Sequence Diagram(s)

sequenceDiagram
  participant Test as Conformance Test
  participant Sidecar as cloud-event-proxy
  participant Consumer as Consumer App
  participant EventAPI as Event API v2

  Test->>Consumer: deploy and WaitForConsumerReady()
  Consumer->>Sidecar: curl /health
  Sidecar-->>Consumer: OK
  Test->>EventAPI: verify initial clockClass
  Test->>Sidecar: kill cloud-event-proxy process
  Test->>Sidecar: WaitForCloudEventProxyReady()
  Sidecar-->>Test: /health OK after restart
  Test->>EventAPI: verifyClockClassCurrentState() via fresh subscription
  EventAPI-->>Test: PushInitialEvent + observed clockClass
Loading
🚥 Pre-merge checks | ✅ 5 | ❌ 10

❌ Failed checks (10 inconclusive)

Check name Status Explanation Resolution
Stable And Deterministic Test Names ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Test Structure And Quality ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Microshift Test Compatibility ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Single Node Openshift (Sno) Test Compatibility ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Topology-Aware Scheduling Compatibility ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Ote Binary Stdout Contract ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Ipv6 And Disconnected Network Test Compatibility ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
No-Weak-Crypto ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Container-Privileges ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
No-Sensitive-Data-In-Logs ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
✅ Passed checks (5 passed)
Check name Status Explanation
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects that this is an upstream sync, though it is broad and does not describe the specific changes.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.


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.

@jzding jzding changed the title CNF-16772, CNF-16780, CNF-19588, CNF-25274, OCPBUGS-7808, OCPBUGS-7811, OCPBUGS-8112: Sync from upstream (08-Jul-2026) CNF-16772, CNF-16780, CNF-19588, CNF-25274, OCPBUGS-7808: Sync from upstream (08-Jul-2026) Jul 8, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jzding: This pull request references CNF-16772 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.

This pull request references CNF-16780 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.

This pull request references CNF-19588 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.

This pull request references CNF-25274 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.

This pull request references Jira Issue OCPBUGS-7808, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.13.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Upstream PRs included

  • #267 chore(deps): bump golang.org/x/net from 0.49.0 to 0.55.0
  • #266 CNF-25274: Add minKubeVersion to CSV for OCP 5.0 certification (CNF-25274)
  • #263 CNF-16772: Add CI tests for GM metric cleanup on PtpConfig deletion (CNF-16772,OCPBUGS-7808,OCPBUGS-7811)
  • #251 PTP CI: verify PTP processes restart and socket cleanup after termination (CNF-16780,OCPBUGS-8112)
  • #171 CNF-19588: CI test for clockClass recovery after cloud-event-proxy crash (CNF-19588)

Summary by CodeRabbit

  • New Features

  • Added support for a minimum Kubernetes version requirement in the operator metadata.

  • Improved event handling to better validate current state after disruptions and support multiple initial event topics.

  • Added readiness checks for consumer workloads before event validation begins.

  • Bug Fixes

  • Strengthened conformance coverage for restarts, proxy recovery, and config deletion/reapply scenarios.

  • Improved restart-state tracking to better detect issues during process recovery.

  • Chores

  • Updated metadata timestamps and refreshed dependency versions.

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.

@jzding jzding changed the title CNF-16772, CNF-16780, CNF-19588, CNF-25274, OCPBUGS-7808: Sync from upstream (08-Jul-2026) CNF-16772, CNF-16780, CNF-19588, CNF-25274: Sync from upstream (08-Jul-2026) Jul 8, 2026
@openshift-ci-robot openshift-ci-robot removed jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 8, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

@jzding: This pull request references CNF-16772 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.

This pull request references CNF-16780 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.

This pull request references CNF-19588 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.

This pull request references CNF-25274 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:

Upstream PRs included

  • #267 chore(deps): bump golang.org/x/net from 0.49.0 to 0.55.0
  • #266 CNF-25274: Add minKubeVersion to CSV for OCP 5.0 certification (CNF-25274)
  • #263 CNF-16772: Add CI tests for GM metric cleanup on PtpConfig deletion (CNF-16772,OCPBUGS-7808,OCPBUGS-7811)
  • #251 PTP CI: verify PTP processes restart and socket cleanup after termination (CNF-16780,OCPBUGS-8112)
  • #171 CNF-19588: CI test for clockClass recovery after cloud-event-proxy crash (CNF-19588)

Summary by CodeRabbit

  • New Features

  • Added support for a minimum Kubernetes version requirement in the operator metadata.

  • Improved event handling to better validate current state after disruptions and support multiple initial event topics.

  • Added readiness checks for consumer workloads before event validation begins.

  • Bug Fixes

  • Strengthened conformance coverage for restarts, proxy recovery, and config deletion/reapply scenarios.

  • Improved restart-state tracking to better detect issues during process recovery.

  • Chores

  • Updated metadata timestamps and refreshed dependency versions.

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.

@jzding

jzding commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn

1 similar comment
@jzding

jzding commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn

@nocturnalastro

Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jzding, nocturnalastro

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:
  • OWNERS [jzding,nocturnalastro]

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

@jzding

jzding commented Jul 15, 2026

Copy link
Copy Markdown
Contributor Author

/verified later @dpopsuev

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Jul 15, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@jzding: This PR has been marked to be verified later by @dpopsuev.

Details

In response to this:

/verified later @dpopsuev

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 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@jzding: 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 5e9ecf0 into openshift:main Jul 15, 2026
11 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 verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants