Skip to content

OCPDOCS CQA MACH-6: CPMSO Provider Configurations and Health Checks Redux - #117206

Open
mburke5678 wants to merge 1 commit into
openshift:mainfrom
mburke5678:mach-6-1
Open

OCPDOCS CQA MACH-6: CPMSO Provider Configurations and Health Checks Redux#117206
mburke5678 wants to merge 1 commit into
openshift:mainfrom
mburke5678:mach-6-1

Conversation

@mburke5678

@mburke5678 mburke5678 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@openshift-ci-robot

Copy link
Copy Markdown

@mburke5678: No Jira issue with key MACH-6 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

https://redhat.atlassian.net/browse/OSDOCS-17046

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 the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 3, 2026

include::modules/machine-health-checks-creating.adoc[leveloffset=+1]

You can configure and deploy a machine health check to detect and repair unhealthy bare metal nodes.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved to a module.


[role="_abstract"]
You can use machine health check short-circuiting to ensure that machine health checks remediate machines only when the cluster is healthy, by configuring the `maxUnhealthy` field in the `MachineHealthCheck` resource.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved from https://github.com/openshift/openshift-docs/pull/117206/changes#diff-4dcba0b1e71613dc3607d7de39037ba614c0c2cd4f8de056ac50748191df095fL49. No need to review beyond the short desc. And changed the H3s to description list entries.

`spec.template.machines_v1beta1_machine_openshift_io.spec.providerSpec.value.network.workspace.server`:: Specifies the vCenter server IP or fully qualified domain name (FQDN).

end::controlplane[]
-- No newline at end of file

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I have no idea....


[role="_abstract"]
You can configure a machine health check by using a `MachineHealthCheck` custom resource (CR).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved from https://github.com/openshift/openshift-docs/pull/117206/changes#diff-9035c4e32d3908a412d19cfcf79271e1f3cfd5bb7a002b8b59c58749d6c79a42L70. But, I did move some things around, re-wrote a few, and added a few. Please do review.

If the power operations did not complete, the metal3 remediation controller triggers the reprovisioning of the unhealthy node unless this is a control plane node or a node that was provisioned externally.
====

[id="mgmt-power-remediation-baremetal-about-creating-mhc-baremetal_{context}"]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


:_mod-docs-content-type: CONCEPT
[id="mgmt-power-remediation-baremetal-about-troubleshooting_{context}"]
= Troubleshooting issues with power-based remediation

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After using one of these methods, unhealthy machines are power-cycled by using Baseboard Management Controller (BMC) credentials.

[id="mgmt-power-remediation-baremetal-about-understanding-remediation-process_{context}"]
== Understanding the annotation-based remediation process

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Converted to description list to remediate an H3 error.

Comment on lines -65 to -68
[NOTE]
====
If the power operations did not complete, the metal3 remediation controller triggers the reprovisioning of the unhealthy node unless this is a control plane node or a node that was provisioned externally.
====

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note is still in the file and renders well in the preview.


.Prerequisites

* The {product-title} is installed using installer-provisioned infrastructure (IPI).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'installer-provisioned infrastructure' rather than 'IPI'. For more information, see RedHat.TermsErrors.

+
--
`metadata.name`:: Specifies the name of the machine health check to deploy.
`metadata.annotations`:: For bare metal clusters, you must include the `machine.openshift.io/remediation-strategy: external-baremetal` annotation in the `annotations` section to enable power-cycle remediation. With this remediation strategy, unhealthy hosts are rebooted instead of removed from the cluster.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'bare-metal clusters' rather than 'bare metal clusters'. For more information, see RedHat.TermsErrors.


In a bare metal cluster, remediation of nodes is critical to ensuring the overall health of the cluster. Physically remediating a cluster can be challenging and any delay in putting the machine into a safe or an operational state increases the time the cluster remains in a degraded state, and the risk that subsequent failures might bring the cluster offline. Power-based remediation helps counter such challenges.
[role="_abstract"]
You can configure and deploy a machine health check to detect and repair unhealthy bare metal nodes, which is critical to ensuring the overall health of the cluster.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'bare-metal nodes' rather than 'bare metal nodes'. For more information, see RedHat.TermsErrors.


[id="machine-health-checks-short-circuiting_{context}"]
== Short-circuiting machine health check remediation

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@openshift-ci-robot

Copy link
Copy Markdown

@mburke5678: No Jira issue with key MACH-6 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

https://redhat.atlassian.net/browse/OSDOCS-17046

Previews:
Deploying machine health checks -- Updated entire assembly.
Changing the RHOSP compute flavor by using a control plane machine set -- Updated module.
Configuring multiple network interface controllers by using machine sets -- Updated module

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 commented Aug 3, 2026

Copy link
Copy Markdown

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

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants