Difference between revisions of "Ansible privilege escalation"

From wikieduonline
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
  
  fatal: [your_machine.com]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}
+
  [[fatal:]] [your_machine.com]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}
  
 +
 +
[[ansible --help]]
 +
Privilege Escalation Options:
 +
  control how and which user you become as on target hosts 
 +
 +
  --become-method BECOME_METHOD
 +
                        privilege escalation method to use (default=sudo), use `ansible-doc -t become -l` to list valid choices.
 +
  --become-user BECOME_USER
 +
                        run operations as this user (default=root)
 +
  -K, --ask-become-pass
 +
                        ask for privilege escalation password
 +
  -b, --become          run operations with become (does not imply password prompting)
  
 
== Related ==
 
== Related ==
 
* <code>[[ansible --help]]</code>
 
* <code>[[ansible --help]]</code>
 +
* <code>[[/etc/ansible/ansible.cfg]]</code> and <code>[[timeout]]=30</code>
  
 
== See also ==
 
== See also ==
 
* {{Ansible}}
 
* {{Ansible}}
 +
 +
[[Category:Ansible]]

Latest revision as of 15:35, 6 January 2022


fatal: [your_machine.com]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}


ansible --help
Privilege Escalation Options:
  control how and which user you become as on target hosts  
  --become-method BECOME_METHOD
                        privilege escalation method to use (default=sudo), use `ansible-doc -t become -l` to list valid choices.
  --become-user BECOME_USER
                        run operations as this user (default=root)
  -K, --ask-become-pass
                        ask for privilege escalation password
  -b, --become          run operations with become (does not imply password prompting)

Related[edit]

See also[edit]

Advertising: