So, I've noticed I have a tendency to do things a little backwards but, I'm
hoping someone can clear something up for me.
Originally, i was using the file/copy module in ansible to copy the
authorized_keys2 file from the ansible server to the node in question. A
colleague of mine stated I
files.
I do something like:
- name: authorized_keys - Erik
action: authorized_key user=erik key={{ lookup('file', 'pubkeys/erik')
}} manage_dir=yes
...where pubkeys/erik is a file with one pubkey per line.
-Erik
On Tue, Jan 14, 2014 at 2:20 PM, BrianAI brian.a
All;
I am building an RPM for a machine using rpm-build. I then need to take
the rpm it built, and I want to use yum to install that. Below is my .yml
playbook and the error that accompanies trying to install it. Any thoughts
would be greatly appreciated. Thanks!!
32 - name:
Also worth noting:
changed: [server1] = {changed: true, cmd: ls
/root/rpmbuild/RPMS/x86_64/iomemory-vsl-$(uname -r)*.rpm , delta:
0:00:00.005180, end: 2013-12-13 13:38:28.657420, item: , rc: 0,
start: 2013-12-13 13:38:28.652240, stderr: , stdout:
Another thing worth noting (sorry for the multiple posts)
server1 REMOTE_MODULE yum
name=[u'/root/rpmbuild/RPMS/x86_64/iomemory-vsl-2.6.32-431.el6.x86_64-2.3.11.183-1.0.el6.x86_64.rpm']
state=present
so it seems OK?
Not sure where that u comes from in the beginning tho
--
You received
Another question folks.
When I try the following bit of code, it seems to choke:
* 10 - name: set cron for any cron-able scripts*
* 11 cron: name={{ item.name }} job={{ item.job }} state=present*
* 12 with_items:*
* 13 - { name: Gather stuff, job: do stuff }*
* 14 - {
Is this still with some issues?
I wanted to keep the src directory the system of record if you will...so
that if I add / delete files from the ansible server i'm executing the
playbook on, it will happen on the destination machine.
I know I could use command: rsync or shell: rsync or whatever,
Thanks for the advice.
1) using .stdout instead of .stdout.lines worked just fine with regards to
the actual command listed above. Thanks!! :)
2) yes, I could build it out and throw it up on a repo (we even have a
local repo at our location), but this gives me the ability to continually
run
I've got it working by specifying the relative path to where i am running
the playbook from, but synchronize seems to not follow the concept of
roles (or it doesn't reference file from the role directory that you're
in.
Any thoughts to that?
--
You received this message because you are
so it seems the space after name= was the problem.
The reason I put that space there is because the syntax highlighting in VIM
completely got thrown off by having name=but either way (even with the
bad syntax highlighting), it still works properly now that i have name=
Thanks :)
--
FC19 just got 1.4.1:
[]$ ansible --version
ansible 1.4.1
and I still can only get it to work with $ in front:
*TASK: [Create user.]
** changed:
[server1] = (item=Ops)*
(vs)
*TASK: [Create user.]
Seems like the cleaner way to do this is probably to just spend the time to
rewrite stuff to roles. I spoke with someone locally about this, and they
showed me the way they were doing it with roles. it seems like what I'm
doing is very similar conceptually, but different in execution. I was
, 2013 5:02:45 AM UTC-8, Michael DeHaan wrote:
* 11 with_items: $accounts_to_add*
*Legacy variable usage, which 1.4 will rightfully warn you about.
Correct:*
*with_items: accounts_to_add*
On Fri, Nov 29, 2013 at 11:03 PM, BrianAI brian.a@gmail.com wrote:
OK, I got it working
Good evening all!
I am new to Ansible (only 2 days in), but am quite excited by the prospects.
I have a laundry list of questions but I figured it'd be best to separate
them into multiple posts to help people searching these lists in the future.
The first question is:
- After much
14 matches
Mail list logo
