Bug 1834542

Summary:	"engine-setup" does not manage DNF configured proxy
Product:	[oVirt] ovirt-engine	Reporter:	Simon Coter <simon.coter>
Component:	Setup.Engine	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Barbora Dolezalova <bdolezal>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4.0	CC:	bugs, gdeolive
Target Milestone:	ovirt-4.5.0	Flags:	sbonazzo: ovirt-4.5+ gdeolive: testing_ack+
Target Release:	4.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0	Doc Type:	Bug Fix
Doc Text:	yum proxy configuration was ignored while running engine-setup. Now engine-setup honor proxy configuration.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-28 09:26:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1417161

Description Simon Coter 2020-05-11 22:10:35 UTC

Description of problem:

Installing ovirt-engine behind a proxy is not automatically managed by "engine-setup".
So, even if "DNF" is configured with proper proxy configuration, the "engine-setup" installation fails and ignore the configured DNF proxy.


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

4.4.0-RC1


How reproducible:

Install ovirt-engine on CentOS-8 behind a proxy (with proxy configured on dnf.conf).
Run "engine-setup" to see installation/configuration failing in the first steps.

Actual results:
Failed ovirt-engine installation/setup.


Expected results:
"engine-setup" intercepts the DNF configured proxy and use it while looking for packages/RPMs.


Additional info:
Work-around: export http_proxy/https_proxy env variables before running "engine-setup".

Comment 1 RHEL Program Management 2020-05-12 00:10:38 UTC

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Sandro Bonazzola 2020-09-09 11:29:03 UTC

I also got report that when proxy is used (adding proxy=... in /etc/yum.conf) and/or exporting http_proxy and https_proxy variables, engine-setup is not reading /etc/yum/vars/contentdir so it then fails downloading reposytory metadata:

[ INFO  ] DNF Errors during downloading metadata for repository 'AppStream':
           - Status code: 404 for http://mirror.centos.org/$contentdir/8/AppStream/x86_64/os/repodata/repomd.xml 

so $contendir is not resolved to "centos"

Looks like we are missing to read the yum config at all here.

Comment 3 Yedidyah Bar David 2022-03-02 08:00:47 UTC

Please try with current master code (would be released eventually as 4.5). I didn't try this manually recently, but we do rely on this in [1] - search the code there for 'socks.proxy|sshd.proxy'. We had to do this for testing IPv6-only setups, because some of our dnf repos are/were IPv4-only.

[1] https://github.com/ovirt/ovirt-system-tests/

Comment 5 Sandro Bonazzola 2022-04-28 09:26:34 UTC

This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 6 Red Hat Bugzilla 2023-09-15 00:31:44 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days