Bug 186054
Summary: | yum doesn't use proxy when launched from sudo context | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | stef <stephane.tranchemer> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-19 20:41:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
stef
2006-03-21 12:37:23 UTC
additional infos : even launched from a root console (after doing a 'su' or 'su -'), you still need to enter 'export http_proxy=http://proxy:8080' before issuing the 'yum upgrade' command. The parameter 'proxy=http://proxy:8080' in /etc/yum.conf is ignored. By default, sudo now does some environment cleaning and only retains a certain set of env vars to avoid the never-ending exploits due to preserved environmental variables. See /etc/sudoers for the list of what's kept. proxy in yum.conf should work though (In reply to comment #2) > proxy in yum.conf should work though Well it doesn't ... here's an example output, the line 'proxy=http://proxy:8080' is present in /etc/yum.conf. [root@yuri ~]# yum upgrade Loading "installonlyn" plugin Setting up Upgrade Process Setting up repositories livna [1/4] core [2/4] Cannot find a valid baseurl for repo: core Error: Cannot find a valid baseurl for repo: core [root@yuri ~]# export HTTP_PROXY=http://proxy:8080 [root@yuri ~]# yum upgrade Loading "installonlyn" plugin Setting up Upgrade Process Setting up repositories livna [1/4] core [2/4] updates [3/4] extras [4/4] Reading repository metadata in from local files No Packages marked for Update/Obsoletion (In reply to comment #2) > By default, sudo now does some environment cleaning and only retains a certain > set of env vars to avoid the never-ending exploits due to preserved > environmental variables. See /etc/sudoers for the list of what's kept. to be complete, the result as shown in comment #3 is ALSO true when running yum from a real root login, not only a 'sudo' or a 'su'. |