New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ansible reads proxy from yum.conf but doesn't handle _none_ #56538
Comments
Files identified in the description: If these files are inaccurate, please update the |
From your error:
it is obvious that you set I am not sure setting the environment variable to needs_info |
In my environment, I was doing:
That triggers this defect. But have changed it to the following and ansible now works again:
So, no, That error message was changed by me into my local source. That was not an ansible error message. The problem was vague until I added extra logging. It was not an environment variable -- In yum, this I quote:
See also other issues brought up in other projects due to how I previously set this in my environment's I propose that ansible's yum module never poke the value |
* yum: handle "_none_" value for proxy Fixes ansible#56538 * Fix sanity check
* yum: handle "_none_" value for proxy Fixes ansible#56538 * Fix sanity check (cherry picked from commit 7b9d7e6)
* yum: handle "_none_" value for proxy Fixes ansible#56538 * Fix sanity check
SUMMARY
This appears to be a regression after upgrading to 2.7.10 from 2.5.x
I'm getting this error:
I modified ansible source to show the value of https proxy to the error message:
_none_
comes fromyum.conf
and is explicitly allowed by yum for yum to disable proxy:https://superuser.com/questions/393099/how-to-specify-that-yum-should-not-use-proxy-for-specific-domain
From yum.conf manual:
My suggestion is when you are reading yum.conf for proxy, treat
_none_
as ''ISSUE TYPE
COMPONENT NAME
ansible/module_utils/urls.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
CentOS 7
STEPS TO REPRODUCE
I am trying to install a package via
yum:
pkg: http://...
EXPECTED RESULTS
That it should work
ACTUAL RESULTS
See stack trace above.
The text was updated successfully, but these errors were encountered: