cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update faq.rst (#63026)

Browse source
This commit is contained in:
Ashley Hardin 2019-11-05 16:55:01 -05:00 committed by Sandra McCann
parent 70d2750e0a
commit 78be0dcbc8
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/docsite/rst/reference_appendices/faq.rst
View file

@ -113,7 +113,7 @@ and run Ansible from there.
.. _python_interpreters: .. _python_interpreters:
How do I handle python not having a Python interpreter at /usr/bin/python on a remote machine? How do I handle not having a Python interpreter at /usr/bin/python on a remote machine?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
While you can write Ansible modules in any language, most Ansible modules are written in Python, While you can write Ansible modules in any language, most Ansible modules are written in Python,
@ -150,12 +150,12 @@ How do I handle the package dependencies required by Ansible package dependencie
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
While installing Ansible, sometimes you may encounter errors such as `No package 'libffi' found` or `fatal error: Python.h: No such file or directory` While installing Ansible, sometimes you may encounter errors such as `No package 'libffi' found` or `fatal error: Python.h: No such file or directory`
These errors are generally caused by the missing packages which are dependencies of the packages required by Ansible. These errors are generally caused by the missing packages, which are dependencies of the packages required by Ansible.
For example, `libffi` package is dependency of `pynacl` and `paramiko` (Ansible -> paramiko -> pynacl -> libffi). For example, `libffi` package is dependency of `pynacl` and `paramiko` (Ansible -> paramiko -> pynacl -> libffi).
In order to solve these kinds of dependency issue, you may need to install required packages using the OS native package managers (e.g., `yum`, `dnf` or `apt`) or as mentioned in the package installation guide. In order to solve these kinds of dependency issues, you might need to install required packages using the OS native package managers, such as `yum`, `dnf`, or `apt`, or as mentioned in the package installation guide.
Please refer the documentation of the respective package for such dependencies and their installation methods. Refer to the documentation of the respective package for such dependencies and their installation methods.
Common Platform Issues Common Platform Issues
++++++++++++++++++++++ ++++++++++++++++++++++
@ -185,8 +185,8 @@ If you want to run under Python 3 instead of Python 2 you may want to change tha
$ pip install ansible $ pip install ansible
If you need to use any libraries which are not available via pip (for instance, SELinux Python If you need to use any libraries which are not available via pip (for instance, SELinux Python
bindings on systems such as Red Hat Enterprise Linux or Fedora that have SELinux enabled) then you bindings on systems such as Red Hat Enterprise Linux or Fedora that have SELinux enabled), then you
need to install them into the virtualenv. There are two methods: need to install them into the virtualenv. There are two methods:
* When you create the virtualenv, specify ``--system-site-packages`` to make use of any libraries * When you create the virtualenv, specify ``--system-site-packages`` to make use of any libraries
installed in the system's Python: installed in the system's Python:
@ -226,7 +226,7 @@ is likely the problem. There are several workarounds:
solaris1 ansible_remote_tmp=$HOME/.ansible/tmp solaris1 ansible_remote_tmp=$HOME/.ansible/tmp
* You can set :ref:`ansible_shell_executable<ansible_shell_executable>` to the path to a POSIX compatible shell. For * You can set :ref:`ansible_shell_executable<ansible_shell_executable>` to the path to a POSIX compatible shell. For
instance, many Solaris hosts have a POSIX shell located at :file:`/usr/xpg4/bin/sh` so you can set instance, many Solaris hosts have a POSIX shell located at :file:`/usr/xpg4/bin/sh` so you can set
this in inventory like so:: this in inventory like so::