Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1687372 - etcd: force-new-cluster flag should never be part of public documentation
Summary: etcd: force-new-cluster flag should never be part of public documentation
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.6.z
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-11 12:03 UTC by Sam Batschelet
Modified: 2019-03-13 05:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Sam Batschelet 2019-03-11 12:03:43 UTC
Description of problem: force-new-cluster is unsafe and should never be documented as a public solution.[1] It seems that we have a bad habit of documenting an unsafe flag as a workaround for proper cluster reconfiguration. If user wants to use this flag then that is out of our control but documenting it as a solution is not responsible as it breaks guarantees given by the consensus protocol. If used wrong can cause panic.


Version-Release number of selected component (if applicable): OpenShift 3.6+


How reproducible: all


Steps to Reproduce:
1. read docs

Actual results: force-new-cluster is used often


Expected results: etcd documentation should included proper steps to manipulate etcd cluster against the Cluster API.


Additional info:

[1]https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/configuration.md#unsafe-flags


Note You need to log in before you can comment on or make changes to this bug.