Bug 1789299

Summary:	etcd backup tool not working with a proxy
Product:	OpenShift Container Platform	Reporter:	Aarne Ojanperä <aarne>
Component:	Etcd	Assignee:	Suresh Kolichala <skolicha>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	lszaszki, scuppett, skolicha, yhe
Target Milestone:	---
Target Release:	4.4.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:23:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aarne Ojanperä 2020-01-09 09:55:18 UTC

Description of problem:

openshift-recovery-tools script does not respect the cluster wide proxy setting. Script tries to download etcdctl directly from the internet and fails as it can't get the package from the DOWNLOAD_URL

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


How reproducible:
very easy


Steps to Reproduce:
1. Configure cluster wide proxy / Install cluster without direct internet connection
2. Log in to master node and run etcd backup per documentation: sudo /usr/local/bin/etcd-snapshot-backup.sh ./assets/backup/snapshot.db

Actual results:
Command hangs on "Downloading etcdctl binary.." and eventually just exists

Expected results:
Successful run

Additional info:

Comment 1 Suresh Kolichala 2020-01-10 18:08:39 UTC

This bug should be closed a duplicate of 1775210. 

When the proxy is enabled, the related environment should be exported to the disaster recovery scripts. The relevant environment variables would be NO_PROXY, HTTP_PROXY, and HTTPS_PROXY.

If the documentation is updated to include the additional steps needed to enable DR scripts to run in a proxied environment, then, DR should work as expected.

The documentation is updated in bug 1775210.

Comment 2 Lukasz Szaszkiewicz 2020-02-21 10:05:54 UTC

Since https://bugzilla.redhat.com/show_bug.cgi?id=1775210 is verified can we close this issue?

Comment 3 Lukasz Szaszkiewicz 2020-02-21 10:25:06 UTC

I'm moving this issue to MODIFIED state per https://bugzilla.redhat.com/show_bug.cgi?id=1789299#c1

Comment 6 ge liu 2020-02-25 10:57:50 UTC

This is doc issue as mentioned above, and I tried it with 4.4, but http_proxy cluster installation blocked with bug: https://bugzilla.redhat.com/show_bug.cgi?id=1806403
so close it and try it after unblock.

Comment 8 errata-xmlrpc 2020-05-04 11:23:24 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