Skip to content

OCPBUGS-104214: Fix etcd restore intro on node recreation - #118937

Open
Pratik-Redhat-Tech wants to merge 1 commit into
openshift:mainfrom
Pratik-Redhat-Tech:OCPBUGS-104214-etcd-restore-docs
Open

OCPBUGS-104214: Fix etcd restore intro on node recreation#118937
Pratik-Redhat-Tech wants to merge 1 commit into
openshift:mainfrom
Pratik-Redhat-Tech:OCPBUGS-104214-etcd-restore-docs

Conversation

@Pratik-Redhat-Tech

Copy link
Copy Markdown

Summary

Since OpenShift 4.18, the standard multi-node etcd restore uses disable-etcd.sh on control plane nodes and cluster-restore.sh on the recovery host. Recreating two control plane nodes is optional, not required.

The intro to "Restoring a cluster manually from an etcd backup" still said the standard restore required complete recreation of 2 control plane nodes. That contradicts the current procedure and can mislead UPI users.

This updates that intro so it matches the 4.18+ restore flow.

Fixes https://issues.redhat.com/browse/OCPBUGS-104214

Test plan

  • Confirm modules/manually-restoring-cluster-etcd-backup.adoc no longer says the standard restore requires recreating 2 control plane nodes
  • Confirm it states that recreating non-recovery control plane machines is optional
  • Confirm it still describes the manual restore as starting a three-member etcd cluster on existing nodes

The standard restore procedure since 4.18 uses disable-etcd.sh and does
not require recreating two control plane nodes. Recreating non-recovery
machines is optional. Stop describing the standard restore as requiring
full recreation of two control plane nodes.

Signed-off-by: Pratik Langde <plangde@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 26, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.1.0) matches configured target version for branch (5.1.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

Summary

Since OpenShift 4.18, the standard multi-node etcd restore uses disable-etcd.sh on control plane nodes and cluster-restore.sh on the recovery host. Recreating two control plane nodes is optional, not required.

The intro to "Restoring a cluster manually from an etcd backup" still said the standard restore required complete recreation of 2 control plane nodes. That contradicts the current procedure and can mislead UPI users.

This updates that intro so it matches the 4.18+ restore flow.

Fixes https://issues.redhat.com/browse/OCPBUGS-104214

Test plan

  • Confirm modules/manually-restoring-cluster-etcd-backup.adoc no longer says the standard restore requires recreating 2 control plane nodes
  • Confirm it states that recreating non-recovery control plane machines is optional
  • Confirm it still describes the manual restore as starting a three-member etcd cluster on existing nodes

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 added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 26, 2026
@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown

Hi @Pratik-Redhat-Tech. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants