Bug 1814581 - [DR] calls to etcdctl should use the container running on host
Summary: [DR] calls to etcdctl should use the container running on host
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.4.0
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On: 1814479
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-18 10:22 UTC by Suresh Kolichala
Modified: 2020-05-04 11:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1814479
Environment:
Last Closed: 2020-05-04 11:46:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 271 0 None open [release-4.4] Bug 1814581: bindata/etcd: run etcdctl inside of container 2020-03-19 11:16:25 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:47:00 UTC

Description Suresh Kolichala 2020-03-18 10:22:17 UTC
+++ This bug was initially created as a clone of Bug #1814479 +++

Description of problem: we currently are extracting an etcdctl image and executing. Since we have a running container with proper certs on host we should use that instead.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: etcdctl is a local binary used by DR


Expected results: exec into etcdctl container and run command.


Additional info:

Comment 5 errata-xmlrpc 2020-05-04 11:46:37 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, 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:0581


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