CNF-16772, CNF-16780, CNF-19588, CNF-25274: Sync from upstream (08-Jul-2026)#711
Conversation
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
…hout socket errors
…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
|
@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:
Comment 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:
Comment 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:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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: 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:
Comment This pull request references Jira Issue OCPBUGS-7811, which is invalid:
Comment This pull request references Jira Issue OCPBUGS-8112, which is invalid:
Comment DetailsIn response to this:
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. |
WalkthroughThis PR adds ChangesCSV Manifest and Dependency Updates
PTP Conformance Test Enhancements
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
🚥 Pre-merge checks | ✅ 5 | ❌ 10❌ Failed checks (10 inconclusive)
✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the 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. Comment |
|
@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:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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: 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. DetailsIn response to this:
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. |
|
/test e2e-aws-ovn |
1 similar comment
|
/test e2e-aws-ovn |
|
/lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified later @dpopsuev |
|
@jzding: This PR has been marked to be verified later by DetailsIn response to this:
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: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Upstream PRs included
Summary by CodeRabbit
New Features
Bug Fixes
Chores