Bug 1322035 - yum per-repository configuration setting of proxy=_none_ is ignored
Summary: yum per-repository configuration setting of proxy=_none_ is ignored
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.7
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Valentina Mukhamedzhanova
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1499211
TreeView+ depends on / blocked
 
Reported: 2016-03-29 15:26 UTC by Jeff Blaine
Modified: 2017-12-06 10:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:15:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jeff Blaine 2016-03-29 15:26:40 UTC
Description of problem:

Setting proxy=_none_ has no effect.

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

yum-3.2.29-69.el6.noarch

How reproducible:

Always

Steps to Reproduce:
1. Configure a proxy in /etc/yum.conf

MINE: proxy=http://proxy.our.org:80

2. Configure a "foo" repository in /etc/yum.repos.d to have proxy=_none_

MINE:
[r701]
name=RHEL6 R701 Repository
baseurl=http://r701-rhel-custom.our.org:5000/RHEL6/$basearch
enabled=1
gpgcheck=0
proxy=_none_

3. Start tcpdump

4. Perform a package installation with yum, targeting a package that ONLY exists in the "foo" repository (where the proxy should not be used):

MINE: yum reinstall -y splunkforwarder --disablerepo='*' --enablerepo=r701

5. tcpdump shows the proxy from /etc/yum.conf being hit

Actual results:

Proxy is hit

Expected results:

Proxy should not be hit

Additional info:

Below shows the yum command as well as the tcpdump output.

~:dev1# grep proxy /etc/yum.conf /etc/yum.repos.d/r701.repo
/etc/yum.conf:proxy=http://proxy.our.org:80
/etc/yum.repos.d/r701.repo:proxy=_none_
~:dev1# echo $http_proxy $https_proxy

~:dev1# yum reinstall -y splunkforwarder --disablerepo='*' --enablerepo=r701
Loaded plugins: product-id, security, subscription-manager
Setting up Reinstall Process
Resolving Dependencies
--> Running transaction check
---> Package splunkforwarder.x86_64 0:6.2.3-264376 will be reinstalled
--> Finished Dependency Resolution

Dependencies Resolved

=====================================================================================================================================
 Package                              Arch                        Version                            Repository                 Size
=====================================================================================================================================
Reinstalling:
 splunkforwarder                      x86_64                      6.2.3-264376                       r701                       13 M

Transaction Summary
=====================================================================================================================================
Reinstall     1 Package(s)

Total download size: 13 M
Installed size: 34 M
Downloading Packages:
splunkforwarder-6.2.3-264376-linux-2.6-x86_64.rpm                                                             |  13 MB     00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
This looks like an upgrade of an existing Splunk Server. Attempting to stop the installed Splunk Server...
splunkd is not running. [FAILED]
  Installing : splunkforwarder-6.2.3-264376.x86_64                                                                               1/1
complete
  Verifying  : splunkforwarder-6.2.3-264376.x86_64                                                                               1/1

Installed:
  splunkforwarder.x86_64 0:6.2.3-264376

Complete!
~:dev1#

*** WHILE THAT WAS HAPPENING, TCPDUMP SHOWS THE FOLLOWING ***

11:21:38.583293 IP dev1.our.org.50005 > proxy.our.org.http: Flags [S], seq 3675945511, win 14600, options [mss 1460,sackOK,TS val 475102731 ecr 0,nop,wscale 7], length 0
11:21:38.583603 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], ack 1711991531, win 115, length 0
11:21:38.583698 IP dev1.our.org.50005 > proxy.our.org.http: Flags [P.], seq 0:91, ack 1, win 115, length 91
11:21:38.662188 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], ack 40, win 115, length 0
11:21:38.662722 IP dev1.our.org.50005 > proxy.our.org.http: Flags [P.], seq 91:344, ack 40, win 115, length 253
11:21:38.742669 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], ack 2800, win 160, length 0
11:21:38.742934 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], ack 4460, win 206, length 0
11:21:38.782845 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], ack 5560, win 229, length 0
11:21:38.823139 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], ack 6178, win 251, length 0
11:21:38.824544 IP dev1.our.org.50005 > proxy.our.org.http: Flags [.], seq 344:6184, ack 6178, win 251, length 5840
11:21:38.824562 IP dev1.our.org.50005 > proxy.our.org.http: Flags [P.], seq 6184:7409, ack 6178, win 251, length 1225
11:21:38.828688 IP dev1.our.org.50005 > proxy.our.org.http: Flags [P.], seq 7409:8276, ack 6178, win 251, length 867
11:21:39.080852 IP dev1.our.org.50005 > proxy.our.org.http: Flags [P.], seq 8276:8601, ack 6253, win 251, length 325
11:21:39.163037 IP dev1.our.org.50005 > proxy.our.org.http: Flags [P.], seq 8601:8654, ack 7634, win 274, length 53
...etc etc...

Comment 2 Jeff Blaine 2016-04-05 19:49:59 UTC
I believe this bug report to be in error. Upon further inspection, I cannot reproduce this. I believe something strange was going on with my usage of --disablerepo='*' --enablerepo='r701'. If I explicitly use --disablerepo for every named repository I want disabled, I get the desired results: I see no traffic to the proxy server.

Comment 3 Jan Kurik 2017-12-06 10:15:24 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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