Skip to content

OSDOCS#17761: node replacement procedure updates#106129

Open
skopacz1 wants to merge 1 commit intoopenshift:mainfrom
skopacz1:OSDOCS-17761
Open

OSDOCS#17761: node replacement procedure updates#106129
skopacz1 wants to merge 1 commit intoopenshift:mainfrom
skopacz1:OSDOCS-17761

Conversation

@skopacz1
Copy link
Contributor

@skopacz1 skopacz1 commented Feb 6, 2026

OSDOCS-17761

Version(s): 4.19+

This PR updates the existing procedure for replacing unhealthy control plane nodes

QE review:

  • QE has approved this change.

Preview:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 6, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 6, 2026

@skopacz1: This pull request references OSDOCS-17761 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 "4.22.0" version, but no target version was set.

Details

In response to this:

OSDOCS-17761

Version(s): 4.19+

This PR updates the existing procedure for replacing unhealthy control plane nodes

QE review:

  • QE has approved this change.

Preview:

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.

@skopacz1 skopacz1 changed the title OSDOCS-17761: node replacement procedure updates OSDOCS#17761: node replacement procedure updates Feb 6, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 6, 2026
@openshift-ci-robot
Copy link

@skopacz1: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

OSDOCS-17761

Version(s): 4.19+

This PR updates the existing procedure for replacing unhealthy control plane nodes

QE review:

  • QE has approved this change.

Preview:

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.

@skopacz1 skopacz1 added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 labels Feb 6, 2026
@skopacz1 skopacz1 added this to the Continuous Release milestone Feb 6, 2026
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 6, 2026
@ocpdocs-previewbot
Copy link

🤖 Fri Feb 06 17:27:12 - Prow CI generated the docs preview:

https://106129--ocpdocs-pr.netlify.app/openshift-enterprise/latest/nodes/nodes/nodes-nodes-replace-control-plane.html

@openshift-ci
Copy link

openshift-ci bot commented Feb 6, 2026

@skopacz1: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-asciidoc 4336ae2 link true /test validate-asciidoc

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.

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

Labels

branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants