Description of problem: If etcd-member-add.sh is ran on an existing etcd member then etcd pod is removed and etcd cluster goes down. # https://docs.openshift.com/container-platform/4.2/backup_and_restore/replacing-failed-master.html#restore-add-master_replacing-failed-master-host Although above doc says "You must run this procedure on the master host that is being added to the etcd cluster", script should check whether the host hasn't been added to etcd cluster already at the beginning itself.
>If etcd-member-add.sh is ran on an existing etcd member then etcd pod is removed and etcd cluster goes down. ># https://docs.openshift.com/container-platform/4.2/backup_and_restore/replacing-failed-master.html#restore-add-master_replacing-failed-master-host > >Although above doc says "You must run this procedure on the master host that is being added to the etcd cluster", script should check whether the host hasn't been added to etcd cluster already at the beginning itself. Multiple our customers broke their cluster due to this. (It didn't become a big problem since every cases happened in their test env...) Although we know that the warning has been written in OCP4's manual, people sometimes make a mistake. To run etcd-*.sh is very risky, so we think it should have some logic to prevent misoperation. We hope that Red Hat will consider to improve it.
This should be fixed in 4.3 z
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Thanks! Moving this back to backlog.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2436