Bug 1721091

Summary: yum doesn't read config file via http any more
Product: Red Hat Enterprise Linux 8 Reporter: Karel Srot <ksrot>
Component: dnfAssignee: Marek Blaha <mblaha>
Status: CLOSED ERRATA QA Contact: Jan Blazek <jblazek>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: allen.payne, amatej, james.antill, jcastran, mblaha, rdulhani
Target Milestone: rcKeywords: AutoVerified, FutureFeature, Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dnf-4.2.17-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:47:49 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:
Bug Depends On: 1681084    
Bug Blocks:    

Description Karel Srot 2019-06-17 10:47:10 UTC
Description of problem:

# yum -c http://localhost/my-yum-config --disableplugin=rhnplugin install test-aaa'
Config error: Config file "http://localhost/my-yum-config" does not exist


Version-Release number of selected component (if applicable):
dnf-4.2.7-1.el8.noarch
libdnf-0.35.1-1.el8.x86_64
librepo-1.10.3-1.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. see above

Actual results:
config file specified with http:// URL is not used

Expected results:
config file specified with http:// URL is used


This is a regression, it was working fine with
dnf-4.2.6-1.el8.noarch
libdnf-0.33.0-1.el8.x86_64
librepo-1.10.1-1.el8.x86_64

Comment 2 Karel Srot 2019-06-17 11:00:54 UTC
FYI, neither HTTPS works.
Is there a list of supported protocols?

Comment 10 Daniel Mach 2019-09-18 12:19:16 UTC
This bug is not a regression within RHEL 8, but a different behavior to RHEL 7.
Removing Regression keyword.

Comment 14 jcastran 2019-11-19 16:35:26 UTC
*** Bug 1774126 has been marked as a duplicate of this bug. ***

Comment 21 errata-xmlrpc 2020-04-28 16:47:49 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:1823