[ansible problem processing] remote execution user environment variable loading problem

Problem phenomenon

Use ansible The command line executes remote commands

Use command modular , There is an error ：[Errno 2] No such file or directory

Same command change shell modular , There is an error ：/bin/sh: ifconfig: command not foundnon-zero return code

Question why

adopt shell Module errors can be clearly found , The command was not found during execution .

So the cause of the problem becomes clear , During remote execution Incomplete loading of environment variables , As a result, some commands cannot be found .

Why does it cause incomplete loading of environment variables ？

ansible When the command line executes a command remotely , It's actually executing non-login shell,non-login shell Only... Will be loaded ~/.bashrc、/etc/bashrc Two documents

About login shell and non-login shell Load profile

login shell Load environment variable order ：/etc/profile --> ~/.bash_profile --> ~/.bashrc --> /etc/bashrc

non-login shell Load environment variable order ：~/.bashrc --> /etc/bashrc

Problem solving

* Method 1 ： modify ansible The configuration file

modify ansible.cfg The configuration file , Switch user implementation login shell, Load environment variables . This method is more appropriate , modify ansible Parameters , For other uses ansible Of users are insensible .

[privilege_escalation]
become=True
become_method=sudo
become_user=root
#become_ask_pass=False
become_flags='-i'

become=True（ must ）, Enable switching users .ansible Command line options correspond to --become or -b

become_method Support sudo perhaps su, If you use su Switching users ,become_flags Need to change to '-' or '-l'.ansible Command line options correspond to --become-method

become_user Fill in the user to switch .ansible Command line options correspond to --become-user

become_flags sudo perhaps su Command options .ansible There is no corresponding option on the command line , You have to write ansible.cfg The configuration file .

Method 2 ： Manually load environment variables

Method 2.1：

You can choose to execute commands or scripts before , Execute first source /etc/profile. But this method needs to manually load environment variables every time it is executed

Method 2.2：

Execute on the remote machine   echo "source /etc/profile" >> /etc/bashrc , Once and for all , But you need a remote machine to perform .

Method 3 ： The command uses an absolute path

This method is the most stupid . Since you just can't get environment variables , Then you only need to use the command every time , Just enter the absolute path of the command .

If you just solve the problem temporarily , I don't want to toss the above two methods , You can use the absolute path first .