Thanks for the tip. It works fine now. I should have used a simple YAML
format checker.
On Monday, November 10, 2014 at 3:31:42 PM UTC-6, Matt Martz wrote:
>
> Your indentation is off. the word "tasks" is indented too far. Here is a
> properly indented playbook:
>
> ---
> - hosts: windows
>
Okay this is fixed. I've discovered that the values assigned to the
variables in ansible\group_vars\windows.yml namely "ansible_ssh_user" and
"ansible_ssh_pass" must:
1. Exactly match an account on the windows machine with admin privileges
(account must exist but need NOT be current act
Okay this is fixed. The values assigned to the variables
"ansible_ssh_user" and "ansible_ssh_pass" must:
1. Exactly match an account on the windows machine with admin privileges
(account must exist but need NOT be current active login)
2. If you are using SSL and the value of
winr
Okay this is fixed. The values assigned to the variables
"ansible_ssh_user" and "ansible_ssh_pass" must:
1. Exactly match an account on the windows machine with admin privileges
(account must exist but need NOT be current active login)
2. If you are using SSL and the value of
winr
It's fixed now. Here's my windows.yml file contents
ansible_ssh_user: ansible
ansivle_ssh_pass: ansible123
ansible_ssh_port: 5986
ansible_connection: winrm
It seems that the 3rd line of my windows.yml file "ansible_ssh_port: 5986"
was not doing it's job because I appended my computer name with
It's fixed now. Here's my windows.yml file contents
ansible_ssh_user: ansible
ansivle_ssh_pass: ansible123
ansible_ssh_port: 5986
ansible_connection: winrm
It seems that the 3rd line of my windows.yml file "ansible_ssh_port: 5986"
was not doing it's job because I appended my computer name with
Here's my windows.yml file contents
ansible_ssh_user: ansible
ansivle_ssh_pass: ansible123
ansible_ssh_port: 5986
ansible_connection: winrm
It seems that the 3rd line of my windows.yml file "ansible_ssh_port: 5986"
was not doing it's job because I appended my computer name with the port
number
On Tuesday, April 21, 2015 at 12:55:59 AM UTC+3, Loc Nguyen wrote:
>
> Hi,
>
> I have a task that copies a folder onto a virtual box machine and then
> uses the command module to execute a shell script in that remote folder.
> Ansible always complains with,
>
> msg: [Errno 8] Exec format error
Awsome! Without the print function I wasn't thinking format. Nice, clear
explanation. Thanks!
Paul
On Saturday, April 25, 2015 at 7:58:11 AM UTC-7, Paul Tötterman wrote:
>
>
> % is the string format operator. 'bar: %s' % 'tada' results in the string
> 'bar: tada'
>
>
--
You received this mess
I'm trying to understand what "['tag_Environment_%s' % args.environment]"
means.
[] is a list literal in Python. [1, 2, 3] can also be written as list(1, 2,
3)
% is the string format operator. 'bar: %s' % 'tada' results in the string
'bar: tada'
['tag_Environment_%s' % args.environment] res
> On Apr 25, 2015, at 1:37 AM, Paul Stivers wrote:
>
> This may be as much a Python question as an Ansible question. This is a
> function in a deploy script.
> I'm trying to understand what "['tag_Environment_%s' % args.environment]"
> means.
> Problem is I don't know enough about the syntax t
Thanks will try this with nodemanager as that is all i need to be running
in the background.
Regards
Nicholas Irving
On 25 Apr 2015 7:02 pm, "Mark Phillips" wrote:
> Hello,
>
> A common problem I've hit a number of times. You can do an async, yes,
> with a massive timeout (99 or such lik
Hi,
I will have a look at how we can do this with the current scripts
developed, as currently a daemon service starts (nodemanager in this case
that does not use any daemin tools other than itself) and attaches to the
root process.
It seems i am coding to solve an issue that does not exist if run
Hello,
A common problem I've hit a number of times. You can do an async, yes, with
a massive timeout (99 or such like). I did have some success with
this once though:
- name: Ensure admin service is started
shell: >
running=$( netstat -ant | grep -cP '7001.+LISTEN' ) ;
[ $runn
Hello,
I've done a lot of demos of this sort of thing using Ansible Tower's
'callbacks' feature. A playbook is exposed as a URL - embed a call to that
URL[1] in user-data when spinning up an instance, and you have a 'phone
home' solution that keeps the beauty of the push model.
--Mark
[1] Her
Evening,
I am trying to keep a spawn process that normally attaches to process id 1
wheb running. However because ansible kills all entries in a process group
i have been told to use async.
However do i wait for the async process to complete before starting the
next task? Does setting a poll time
16 matches
Mail list logo
