After - option, this coming up. any idea, what's going on??
fatal: [X.X.X.X]: UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: OpenSSH_7.6p1
Ubuntu-4ubuntu0.5, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading
configuration data
Hi Felix,
Thanks for your email and the link.
https://docs.ansible.com/ansible/latest/collections/community/general/tss_lookup.html
I saw the link but not sure how do i add into my ansible play book to fetch
the credentials i wanted.
On Fri, Aug 20, 2021 at 10:57 AM 'Felix Fontein' via Ansible
Are you able to ssh from the control node to the client as that user? If
so, does it fail, or are you able to log in. If you are able to log in,
then you might have a problem with your ansible command syntax.
Personally, when I run a playbook, I have to specify the user ( -u ) and I
also have to
Which inventory file do you use ? And try to run the playbook with -
for debugging purposes. If you can share the output of the debugging
command would be great !
On Thu, Sep 2, 2021, 3:04 PM aman kumar chagti
wrote:
> I tried these methods..same error coming up
>
> On Thursday, September
The ssh test you made is using the ansible controller server ?
Are you sure you are using the good ansible user on the target host ?
(-u parameter for ansible-playbook)
Regards,
JY
Le 02/09/2021 à 14:48, aman kumar chagti a écrit :
yes, sshpass is inistalled
On Thursday, September 2,
I tried these methods..same error coming up
On Thursday, September 2, 2021 at 7:13:52 PM UTC+5:30 e.ht...@gmail.com
wrote:
> Hello,
> From one side, when using become: yes, verify if the root password on the
> managed nodes is the same as the controller, otherwise use -k and specify
> the
Hello,
>From one side, when using become: yes, verify if the root password on the
managed nodes is the same as the controller, otherwise use -k and specify
the root managed node password.
>From another side, when using a dedicated user for ansible, verify if that
user exist and is a sudoer on the
Le 02/09/2021 à 14:53, aman kumar chagti a écrit :
@jyle if sshpass needs to be installed on target VM as well??
Nope, only on server side
Regards,
JYL
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group
I've given privilege escalation in playbook i.e, *become: yes*
On Thursday, September 2, 2021 at 6:22:29 PM UTC+5:30 aman kumar chagti
wrote:
> how to give privilege escalations?
>
> On Thursday, September 2, 2021 at 6:18:49 PM UTC+5:30 aman kumar chagti
> wrote:
>
>> how to do that??
>
>
>>
@jyle if sshpass needs to be installed on target VM as well??
On Thursday, September 2, 2021 at 6:06:44 PM UTC+5:30 jyle...@gmail.com
wrote:
> If you want password authentication, you need sshpass on your ansible
> controller server. Did you install it ?
>
> Regards,
>
> JYL
>
>
> Le
how to give privilege escalations?
On Thursday, September 2, 2021 at 6:18:49 PM UTC+5:30 aman kumar chagti
wrote:
> how to do that??
>
>
> On Thursday, September 2, 2021 at 5:59:48 PM UTC+5:30
> komalsuth...@gmail.com wrote:
>
>> Have you given privilege escalations try doing that.
>>
>> On
how to do that??
On Thursday, September 2, 2021 at 5:59:48 PM UTC+5:30
komalsuth...@gmail.com wrote:
> Have you given privilege escalations try doing that.
>
> On Thu, Sep 2, 2021, 5:25 PM aman kumar chagti
> wrote:
>
>> when I try to run the playbook on a remote VM using password-based
>>
yes, sshpass is inistalled
On Thursday, September 2, 2021 at 6:06:44 PM UTC+5:30 jyle...@gmail.com
wrote:
> If you want password authentication, you need sshpass on your ansible
> controller server. Did you install it ?
>
> Regards,
>
> JYL
>
>
> Le 02/09/2021 à 13:55, aman kumar chagti a
If you want password authentication, you need sshpass on your ansible
controller server. Did you install it ?
Regards,
JYL
Le 02/09/2021 à 13:55, aman kumar chagti a écrit :
when I try to run the playbook on a remote VM using password-based
authentication, I'm getting the following error:
Have you given privilege escalations try doing that.
On Thu, Sep 2, 2021, 5:25 PM aman kumar chagti
wrote:
> when I try to run the playbook on a remote VM using password-based
> authentication, I'm getting the following error:
>
> *fatal: [X.X.X.X]: UNREACHABLE! => {"changed": false, "msg":
when I try to run the playbook on a remote VM using password-based
authentication, I'm getting the following error:
*fatal: [X.X.X.X]: UNREACHABLE! => {"changed": false, "msg": "Failed to
connect to the host via ssh: x...@X.X.X.X: Permission denied
(publickey,password).", "unreachable":
Ok . thanks
On Thu, Sep 2, 2021 at 12:04 PM Abhijeet Kasurde
wrote:
> Hi Jitendar,
>
> You need to write your callback plugin based upon the default callback
> plugin.
>
> You can take inspiration from -
>
>
>1. Developing callback plugin -
>
>
Hi Jitendar,
You need to write your callback plugin based upon the default callback
plugin.
You can take inspiration from -
1. Developing callback plugin -
https://docs.ansible.com/ansible/latest/dev_guide/developing_plugins.html#callback-plugins
2. You need to override the method
Sure .
stdout: # Maintainance Check #
CRITICAL
154 4145 65541 871 hm
PLAY RECAP
19 matches
Mail list logo
