Replacement of the unhealthy etcd member doesn't work with node being automatically rebooted

Solution In Progress - Updated -

Issue

Trying to follow the official documented procedure to replace a failed ETCD member on bare metal IPI clusters makes the cluster almost completely unavailable and impossible to proceed with the replacement once the master is shutdown or removed on the first steps.
Seeing nodes being rebooted automatically which disrupts the entire process.
Deleting selfnoderemediations CRs doesn't work as they keep getting recreated.

Environment

Red Hat OpenShift Container Platform 4.14+ Bare Metal IPI with Workload Availability for Red Hat OpenShift:
- Red Hat Node Healthcheck operator
- Red Hat Self-node Remediation operator
- Red Hat Node Maintenance operator

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content