Bug 1812236 - etcdctl cannot find cert
Summary: etcdctl cannot find cert
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Luis Sanchez
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks: 1812242
TreeView+ depends on / blocked
 
Reported: 2020-03-10 19:35 UTC by Luis Sanchez
Modified: 2020-08-04 18:04 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1812242 (view as bug list)
Environment:
Last Closed: 2020-08-04 18:04:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 249 0 None closed Bug 1812236: etcdctl cannot find cert 2020-10-18 12:58:09 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-08-04 18:04:42 UTC

Description Luis Sanchez 2020-03-10 19:35:57 UTC
Description of problem:

etcdctl run in in etcd pod cannot find crypto materials.

$ oc project openshift-etcd
$ oc exec $(oc get pods --selector app=etcd -o name | head -n 1) etcdctl member list 
Defaulting container name to etcdctl.
Use 'oc describe pod/etcd-ip-10-0-140-99.us-west-1.compute.internal -n openshift-etcd' to see all of the containers in this pod.
Error: open /etc/kubernetes/static-pod-resources/etcd-certs/secrets/etcd-all-peer/etcd-peer-ip-10-0-140-99.us-west-1.compute.internal.crt: no such file or directory
command terminated with exit code 128
$

Comment 5 errata-xmlrpc 2020-08-04 18:04:39 UTC
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 (OpenShift Container Platform 4.5 image release 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:2409


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