Repository navigation
NO-JIRA: [release-4.22] Revert #10106 - #10138
redhat-chai-bot wants to merge 1 commit into
Conversation
Revert openshift#10106 on release-4.22 to restore the preceding etcd-client Service configuration and generated fixtures. Remove the peer-certificate comments and tests introduced by that PR without changing certificate generation logic or subsequent unrelated changes. This reverts commit 61f1748, reversing changes made to db8d227. Assisted-by: OpenAI Codex Signed-off-by: Chai Bot <chai-bot@redhat.com>
|
Pipeline controller notification This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration. Use |
|
@redhat-chai-bot: This pull request explicitly references no jira issue. 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. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-4.22 #10138 +/- ##
================================================
- Coverage 37.43% 37.42% -0.02%
================================================
Files 782 782
Lines 96235 96232 -3
================================================
- Hits 36024 36012 -12
- Misses 57331 57340 +9
Partials 2880 2880
🚀 New features to boost your workflow:
|
|
@redhat-chai-bot: 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. |
|
Coverage triage for the current head:
Retaining the certificate unit tests while reverting the Service change is a possible scoped adjustment, but would no longer be the exact inverse currently described. Awaiting that scope decision; no coverage configuration changes, overrides, or retests were made. Other CI remains pending. AI-generated. Review for accuracy. |
What this PR does / why we need it:
Reverts #10106 on release-4.22.
Restore the headless etcd-client Service manifest and all five generated service fixtures, including their desired-state hashes. Remove the peer-certificate comments and unit tests introduced by #10106. Certificate-generation executable logic is unchanged. Preserve subsequent unrelated release-4.22 changes.
Which issue(s) this PR fixes:
None; this is a NO-JIRA revert of #10106.
Special notes for your reviewer:
This is the exact inverse of merge commit 61f1748 relative to its first parent. No Service migration or replacement logic is added. Existing allocated-IP-to-headless transitions are not validated by the focused tests.
Local checks passed on the unchanged revert with upstream Go1.26.0:
make lint-fix,make verify,make test NUM_CORES=4,make build, and the completemake pre-commit NUM_CORES=4. The final aggregate run exited 0 in 26m27s, including binary/test compilation, generation, verification and the full race-enabled unit suite. Final generation/clean-diff, whitespace and exact-inverse checks passed. This does not claim execution in the exact Red Hat CI image.An earlier aggregate run failed two
support/konnectivityproxytests (proxy read unexpected EOF; canceled-context resolution returned nil), and a bounded retry timed out. Those historical results remain recorded. The latest complete aggregate run passed, including that package, without source changes, test skips, weakened flags or proxy/DNS setting changes. The earlier failures' cause is not established.Checklist:
AI-generated. Review for accuracy.
@devguyio requested from Slack