Bug 1715807

Summary: man page dnf.conf weak about proxy settings and other proxy issues
Product: [Fedora] Fedora Reporter: Terje Røsten <terje.rosten>
Component: dnfAssignee: Jaroslav Rohel <jrohel>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 29CC: amatej, dmach, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 23:13:55 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 Terje Røsten 2019-05-31 10:47:43 UTC
Description of problem:

$ rpm -q dnf
dnf-4.2.5-1.fc30.noarch

I have global proxy setting in /etc/dnf/dnf.conf, which I want to override
in some /etc/yum.repos.d/*.repo files.


From 

$ man dnf.conf

I read:

""""
proxy  string
  URL  of  a proxy server to connect through. If none is specified
  then direct connection is used (the default).
"""

While yum.conf from yum-3.4.3 has:

"""
proxy URL to the proxy server for this repository. Set to '_none_' to disable the global proxy setting for this repository. If this is unset it inherits it from the global setting
"""

From these I was thinking a simple conversion:

proxy=_none_ 
 ->  
proxy=none 

worked, however that's not true.

To unset proxy from global setting with dnf you have to use 

proxy=

(that is to set proxy to nothing)

My request is to describe this better in dnf.conf(5) and also to support the
old yum syntax of proxy=_none_.

The error message with incorrect proxy settting is btw very weak, if user does:

proxy=none 

is just a plain hang, no feedback at all. This should also be improved.

Comment 1 Jaroslav Rohel 2019-08-16 06:25:28 UTC
1. Better documentation of "proxy" option
 PR https://github.com/rpm-software-management/dnf/pull/1457

2. For backward compatibility added support "_none_" value for repo option "proxy"
 PR https://github.com/rpm-software-management/libdnf/pull/710

3. proxy=none
> is just a plain hang, no feedback at all.
There is feedback: "Error: Failed to download metadata for repo 'fedora'"

Yes, you do not know why the error occured. The solutions is to try it again with "-v" argument. Then you get more details about the error.
Cannot download 'https://mirrors.fedoraproject.org/metalink?repo=fedora-30&arch=x86_64': Cannot prepare internal mirrorlist: Curl error (5): Couldn't resolve proxy name for https://mirrors.fedoraproject.org/metalink?repo=fedora-30&arch=x86_64 [Could not resolve proxy: none].
So, there is information "Could not resolve proxy: none"

Comment 2 Ben Cotton 2019-10-31 18:57:06 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-11-27 23:13:55 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.