-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
in 2.13 some modules fail apparently trying to use local python path instead of remote. #78243
Comments
|
Files identified in the description: If these files are incorrect, please update the |
|
At a minimum, we're going to need the full output with at least |
|
This is probably an issue with the BSD port itself as they traditionally rewrite the 'python location' to match the BSD platfrom (it does not know about remotes). |
3 modules acting on one file: file, copy, ini_file. last one seems to be trying wrong python right from the start. |
|
Yeah, this is as we assumed. This is an issue with the FreeBSD ansible (e.g. Because they have modified the shebang in the module file, our shebang replacer doesn't work properly. Specifically, due to the addition of In order for it to match, you would have to be able to set an Since this is not an ansible problem, but a problem with FreeBSD packaging, I'm going to close this. You may want to open a bug report with FreeBSD. If you have further questions please stop by IRC or the mailing list:
|
|
2.12 port has the same shebang, but works. Was something changed in 2.13 that now requires special handling of shebangs in modules? |
|
2.13 addressed a bug where the shebang of the module was not being properly consulted when doing shebang replacements via This was an expected change, and the prior behavior was incorrect. This is still a bug with FreeBSD packaging. |
|
Do I understand correctly that shebangs in modules should now be either unversioned or absent entirely? |
|
They should preferably be left untouched with a value of The shebang is replaced during runtime execution, with either the result of interpreter discovery, or the explicitly set |
Summary
Trying ansible 2.13 on FreeBSD control host, Linux target host. Some modules fail while apparently trying to use python path from local machine.
Issue Type
Bug Report
Component Name
core
Ansible Version
Configuration
OS / Environment
FreeBSD 13.1, Ubuntu 20.04
Steps to Reproduce
on FreeBSD control host use any of affected modules (timezone, mount, sysctl, ini_file, alternatives, selinux) to deploy to a linux host. (There may be others affected).
Among not affected: debug, copy, template, group_by, assert, shell, command, systemd, stat, file, service...
Expected Results
Modules work correctly using discovered python on remote host (
/usr/bin/python)Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: