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
New install of 2.10.5 via Pip (3) results in no binaries #73390
Comments
Files identified in the description: If these files are incorrect, please update the |
That output doesn't seem to indicate it found another Ansible install, but I cannot reproduce this on a clean EL7 (In my case I used a docker container). Without the ability to reproduce this, you will likely need to repeat the steps and run the |
@hinchliff I'd like to add that installing packages with pip into system-wide locations is a bad idea because conflicting with files that yum/dnf claims may damage the system. |
Ok, I uninstalled ansible, and reinstalled with
Resulting in huge output file, captured in this gist: https://gist.github.com/hinchliff/cd6e288291ef35e2f0fd4144525bf4dd And still no luck running ansible / no binaries available:
Setuptools info
|
I see this in the verbose logs
And that binary does exist. Just not on my path, i guess?
hmmm... |
Yes, depending on how the software is built (like CPython), the paths may be different in different OSs, or even if there are several different interpreters on the same system. |
Yeah, searching around it looks like the behavior of This all used to work with ansible 2.9.x (2.9.6 specifically) that we have been using, where the ansible "binaries" were installed to |
I suspect the easiest thing in my case might be to pass in extra options to the pip command, like |
I don't think our distribution package specifies where to install scripts. It should be up to pip/CPython. |
Is This A Bug?Hi! Thanks very much for your submission to Ansible. It sincerely means a lot to us. We're not sure this is a bug, and we don't mean for this to be confrontational. Let's explain what we're thinking:
As such, we're going to close this ticket. However, we're open to being corrected, should you wish to discuss. You can stop by one of our two mailing lists
Comments on closed tickets aren't something we monitor, so if you do disagree with this, a mailing list thread is probably appropriate. Thank you once again for this and your interest in Ansible! |
SUMMARY
Started a new system, running RHEL 7.9, using Python 3.6.8 and pip 21.0. Used pip to install ansible 2.10.5, and while no errors were given, the resulting installation is missing the expected ansible "binaries" -- e.g. in
/usr/bin/ansible
ISSUE TYPE
COMPONENT NAME
pip packaging
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
Starting from a fresh install of RHEL 7, using the root user:
EXPECTED RESULTS
Have binaries installed
ACTUAL RESULTS
No ansible "binaries" are available. It is not possible to run ansible commands:
Is there a default installation of older ansible (using Python 2)? Does that need to be removed? Should this be captured in the ansible pip installation, like from #70348 ? But I don't think there is any previous version installed...
The yum package is not installed:
The text was updated successfully, but these errors were encountered: