On Wednesday, April 25, 2018 at 4:31:05 PM UTC+5:30, ali.k...@aurea.com
wrote:
>
> i have a simple ansible playbook that i am using to configure some windows
> machines. i am getting the following error. i have installed powershell.
> is it the bash shell that is complaining? winrm is confi
I am using the following ansible settings:
ansible_user: 'myuser'
ansible_password: 'mypass'
ansible_port: 5986
ansible_connection: winrm
ansible_winrm_transport: kerberos
ansible_winrm_server_cert_validation: ignore
ansible_winrm_message_encryption: always
ansible_winrm_kerberos_delegation: true
Become and Windows was still experimental in Ansible 2.4 but not much
changed between 2.4 to 2.5+ apart from new features being added. Are you
able to try and run your task with the following vars set to rule out an
incorrect password being set;
- module:
vars:
ansible_become: yes
ans
use the 'raw' module:
ansible openvms-01 -m raw -a "command"
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr.
Hello,
I am trying to use Netconf_config model on Cisco switch catalyst 9300.
I am getting following error message.
You can see the playbook and the running the palybook. I tried with
different options like changing the RPC, indentation and changing the XML
to content in playbook. But nothing w
Hi all,
First timer here.
So the details of the issue are:
Using Ansible 2.6.4
Playbook that runs my custom windows module (wrapping Service Fabric
functionality to create and expand Service Fabric standalone clusters)
It runs on a host server running Windows Server 2016 and has local admin
p
Have you posted all the warnings provided? If so, it looks like you've
disabled the script plugin, which is necessary to parse the contrib
scripts. Check your ansible.cfg [inventory] enable_plugins section and the
ANSIBLE_INVENTORY_ENABLED environment var.
If you just left out some of the warni
if i enable the any_errors_fatal, if there is no error in the script and if
it executes second.yml, it shut downs the server.
when the server is unreachable. because of the any_errors_fatal the script
stops at second.yml.
i want the script to run third.yml and fouth.yml if there is no error in
Not sure putting such information in some version control system is the
wisest, but if you do have it under version control of some type, the
version control mechanism should be able to tell if it has been updated.
You would then just have to have ansible run the version control command to
che
Thanks Jonathan for your reply.
But it is part of the use case, I am trying to achieve it.
Is there way to achieve it.
Regards
Sumit Sahay
7044112109
On Wednesday, 24 October 2018 17:16:19 UTC+5:30, Jonathan Lozada De La
Matta wrote:
>
> That just seems like bad practice. I wouldn't recommend
10 matches
Mail list logo