OCPBUGS-85515: Verify dynamic revision bump for etcd during kernel crash by kasturinarra · Pull Request #31166 · openshift/origin

kasturinarra · 2026-05-13T08:11:18Z

Manual cherry pick of https://github.com/openshift/origin/pull/30915/changes

coderabbitai · 2026-05-13T08:11:28Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 465dbc27-5f21-4145-b893-08508bf0a625

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ 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-robot · 2026-05-13T08:13:30Z

@kasturinarra: This pull request references Jira Issue OCPBUGS-85515, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-85515 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Manual cherry pick of https://github.com/openshift/origin/pull/30915/changes

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.

kasturinarra · 2026-05-13T08:23:24Z

/jira refresh

openshift-ci-robot · 2026-05-13T08:23:29Z

@kasturinarra: This pull request references Jira Issue OCPBUGS-85515, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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:

/jira refresh

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.

kasturinarra · 2026-05-13T08:26:45Z

/jira refresh

openshift-ci-robot · 2026-05-13T08:26:50Z

@kasturinarra: This pull request references Jira Issue OCPBUGS-85515, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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:

/jira refresh

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.

kasturinarra · 2026-05-13T08:30:08Z

/jira refresh

openshift-ci-robot · 2026-05-13T08:30:16Z

@kasturinarra: This pull request references Jira Issue OCPBUGS-85515, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-84500 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-84500 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

Details

In response to this:

/jira refresh

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 · 2026-05-13T08:42:27Z

@kasturinarra: 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.

kasturinarra · 2026-05-13T09:27:55Z

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-ipv6-recovery

openshift-ci · 2026-05-13T09:28:01Z

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

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-ipv6-recovery

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/06dfc3c0-4eae-11f1-8820-b8a6c1af4a8e-0

kasturinarra · 2026-05-13T09:29:22Z

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery

openshift-ci · 2026-05-13T09:29:26Z

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

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-1of3
periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-2of3
periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-3of3

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3a6b69b0-4eae-11f1-9a26-58b1ef10be14-0

kasturinarra · 2026-05-13T14:26:05Z

/verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-31166-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-2of3/2054494354877190144

openshift-ci-robot · 2026-05-13T14:26:17Z

@kasturinarra: This PR has been marked as verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-31166-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-2of3/2054494354877190144.

Details

In response to this:

/verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-31166-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-2of3/2054494354877190144

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.

jaypoulz · 2026-05-13T15:08:24Z

/lgtm
/approved

jaypoulz · 2026-05-13T15:08:41Z

/approve

jerpeter1 · 2026-05-13T15:56:37Z

/label backport-risk-assessed

sosiouxme

/approve

sosiouxme · 2026-05-13T17:57:29Z

 	})

-	g.It("should leave a backup container behind for debugging when etcd container crashes", func() {
+	g.It("should compute etcd revision bump and preserve backup container after kernel panic recovery", func() {


Please note that when a test name is changed or the test is retired, the mapping should be updated so that sippy component readiness can analyze appropriately.

openshift-ci · 2026-05-13T17:58:10Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jaypoulz, kasturinarra, sosiouxme

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~~ [sosiouxme]

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

openshift-ci-robot · 2026-05-13T18:02:32Z

@kasturinarra: Jira Issue Verification Checks: Jira Issue OCPBUGS-85515
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-85515 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Manual cherry pick of https://github.com/openshift/origin/pull/30915/changes

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.

Verify dynamic revision bump for etcd during kernel crash

e0dff45

openshift-ci Bot requested review from jeff-roche and p0lyn0mial May 13, 2026 08:11

kasturinarra changed the title ~~Verify dynamic revision bump for etcd during kernel crash~~ OCPBUGS-85515: Verify dynamic revision bump for etcd during kernel crash May 13, 2026

openshift-ci-robot added 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 May 13, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 13, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 13, 2026

openshift-ci Bot assigned jaypoulz May 13, 2026

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

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 13, 2026

openshift-ci Bot assigned adambkaplan, dgoodwin, gangwgr, jadhaj, kasturinarra, moebasim, pamoedom, prabhapa and prietyc123 May 13, 2026

sosiouxme reviewed May 13, 2026

View reviewed changes

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

openshift-merge-bot Bot merged commit ab5bb65 into openshift:release-4.22 May 13, 2026
8 checks passed

Conversation

kasturinarra commented May 13, 2026

Uh oh!

coderabbitai Bot commented May 13, 2026

Review skipped

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

kasturinarra commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

kasturinarra commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

kasturinarra commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

kasturinarra commented May 13, 2026

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

kasturinarra commented May 13, 2026

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

kasturinarra commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

jaypoulz commented May 13, 2026

Uh oh!

jaypoulz commented May 13, 2026

Uh oh!

jerpeter1 commented May 13, 2026

Uh oh!

sosiouxme left a comment

Choose a reason for hiding this comment

Uh oh!

sosiouxme May 13, 2026

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants