Bug 2076174 - Creating a single-node etcd cluster instructions fail
Summary: Creating a single-node etcd cluster instructions fail
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Latha S
QA Contact: ge liu
Latha S
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-18 06:25 UTC by Michael Washer
Modified: 2023-08-09 12:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-22 10:08:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Washer 2022-04-18 06:25:39 UTC
Document URL: 
https://docs.openshift.com/container-platform/3.11/admin_guide/assembly_restore-etcd-quorum.html#cluster-restore-etcd-quorum-single-node_restore-etcd-quorum

Section Number and Name: 
Creating a single-node etcd cluster 

From Step 2 onward, the instructions do not work out of the box with a fresh cluster.

Describe the issue: 
[1] The following file from Step2 is not present by default. This requires `etcd` to be installed in the default namespace. 
`
    /usr/lib/systemd/system/etcd.service
`
This can be resolved by ensuring that `rpm -qa etcd` is present or running `yum install -y etcd`.

[2] In fresh clusters, ETCD certificates are protected and only accessible with `root` permissions. The `/usr/lib/systemd/system/etcd.service` file is configured to use `etcd` user. This should be changed to `root`.

[3] Step 3 must specify the certificates/endpoints, or ensure that the ETCD server will serve insecure clients

Suggestions for improvement: 
Replace the reference to `/usr/lib/systemd/system/etcd.service` with the values expected for the systemctl command.

Additional information: 
This issue was experienced in a customers cluster and then reproduced on Red Hat's quicklab clusters.


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