ons 2018-03-21 klockan 06:40 -0700 skrev Camille Beaudou:
> I'm trying to install Ansible on a Ubuntu 16.04 VM (VMWare). I'm
> following the install instruction on Ansible website, however when
> executing the command "make rpm", i get the following error message
> ...
How did you end up at those
sön 2018-01-21 klockan 16:57 -0800 skrev Joli Martinez:
> I am looking for a way to make vim the default editor on my Ubuntu
> and Debian based system. Could you help me accomplish this? On the
> CLI I know that I have to run "update-alternatives --config editor"
> and then hit 3 for vim. I
ons 2017-12-27 klockan 22:30 -0800 skrev Heather Luna:
> I have a configuration (.conf) file that I'm attempting to manipulate
> by adding the {{ fdqn_hostname }} ONLY for the serverName piece, the
> rest of the information like the SSL password is something that's
> going to change across my
tis 2017-12-26 klockan 23:45 -0800 skrev Nuwan Vithanage:
> curl -k -O
> https://releases.ansible.com/awx/setup/ansible-tower-setup-latest.tar.gz
Please noone take this literally, and actually use the -k/--insecure
option when downloading software.
// Andreas
--
You received this message
lör 2017-09-30 klockan 22:41 -0700 skrev Sivakumar Lakshminarayanan:
> When trying ansible xml module...
> ...
> ...
> ansible 2.3.1.0
According to https://docs.ansible.com/ansible/latest/xml_module.html
the xml module wasn't introduced until Ansible 2.4.
// Andreas
--
You received this
fre 2017-09-29 klockan 14:03 -0700 skrev indraj joglekar:
> How does the git module work?
>
> a) Does it do a pull on the remote server?
> b) Does it first do a pull on the local admin server and then rsync
> copy the repo to the remote server?
The clone/pull happens locally on the remote server.
sön 2017-07-16 klockan 22:15 -0700 skrev Kannappan M:
> Can some one please guide how to learn yaml codings from
> basics to expert level to write in ansible playbooks
What YAML resources have you managed to find on your own? Which
concepts make sense and which don't?
// Andreas
--
You
sön 2017-07-16 klockan 11:16 -0700 skrev Kannappan M:
> Am new to ansible can some one please guide how and
> where to start, and also let me know how to write yaml
> codding effectively any books or links
https://docs.ansible.com/ansible/intro.html is a good starting point.
lör 2017-07-15 klockan 11:04 -0700 skrev NixGeek:
> man one reason ansible makes me crazy is the silly indented crap in
> the playbook.
That "silly indented crap" is more formally referred to as YAML. For
better or worse it's fairly commonly used. Investing a bit of time in
understanding YAML
lör 2017-07-15 klockan 09:18 -0700 skrev NixGeek:
> My playbook
> ==
> ---
>
> - hosts: myhosts
> tasks:
>
> - group:
> name: useradmins
> state: present
> ===
It looks as if you have gotten the indentation wrong.
tis 2017-01-17 klockan 01:42 -0800 skrev Igor Schaefer:
> Sure, all you know the situation, when you install a new version of
> package and you get a dialog window with warnings like "use existing
> version of config file or replace it with new one" or "that your
> lovely function is depricated
ons 2017-01-11 klockan 02:38 -0800 skrev SR:
> I tried installing ansible on centos vagrant, but can’t install. As
> Im new to this, request some one to help me on this.
Easiest is probably to install Ansible from EPEL. If nothing else it's
not unlikely that you might want that repository for
tis 2017-01-10 klockan 21:59 -0800 skrev Mona Gopal:
> Even i am trying to source the bashrc file on my target system.
> Ansible runs successfully without errors but doesn't source the file.
> Below is my task:
>
> - name: source bashrc file
> shell: source ~/.bashrc
> args:
>
ons 2017-01-04 klockan 13:25 +0100 skrev Cosimo Streppone:
> ...
> I'm still unsure about this error message when the facts gathering is
> not happening:
>
> "Could not detect which package manager to use. Try gathering facts
> or setting the \"use\" option."
>
> what is the "use" option?
See
Hello Cosimo
Indeed it looks as if facts aren't being gathered, which is kind of
odd, since it should happen by default. By then each play should
contain the following at the start.
TASK [setup]
***
ok: [localhost.localdomain]
sön 2017-01-01 klockan 10:37 -0800 skrev 'Michael Pophal':
> I'm very keen on this module, but unfortunately I've no idea how to
> install it. Could you please drop a hint, I'm just a ansible user ;-)
Well, here is how I installed it. The following commands being relative
to the playbook
ons 2016-12-07 klockan 23:40 -0800 skrev Sebastian S.:
> which ansible says: /usr/local/bin/ansible
That looks more like somewhere where Pip would install Ansible, or
where someone would install Ansible manually. Any chance that you also
have a /usr/bin/ansible, which better match the apt
ons 2016-12-07 klockan 03:52 -0800 skrev Sebastian S.:
> ansible@DE9899S76 ~ % ansible --version
> ansible 2.0.0.2
>
> 3. apt-cache --showpkg ansible says it' 2.2.0.0
What does `which ansible` say?
That is, any chance that you have an additional version of Ansible
installed, in addition to
Ok, here is a minimal playbook showing my particular issue.
---
- hosts: localhost
vars:
foo: pwfile
tasks:
- name: lookup /etc/passwd
stat: path=/etc/passwd
register: abc_{{ foo }}_def
- name: Display abc_{{ foo }}_def content
debug:
fre 2016-12-02 klockan 15:16 -0800 skrev ja...@blendlabs.com:
> {"failed": true, "invocation": {"module_args": {"cache_valid_time":
> null, "deb": null, "default_release": null, "dpkg_options": "force-
> confdef,force-confold", "force": false, "install_recommends": null,
> "name": ["cryptsetup",
Greetings
Since moving from Ansible 2.1.3 to Ansible 2.2.0 I have run into an
issue with register, and when it's variable name is built up using a
variable. I have no idea if this is due to a regression in Ansible 2.2,
or if I have been doing something wrong/unsupported which I finally got
bitten
On ons, 2016-05-11 at 03:28 -0700, codfather wrote:
> Andreas, when I implemented this, I had to put a line in the section
> to use sudo for the installation, which makes sense, just wondering
> if you had achieved that another way , just curious.
Yepp, I have the following in my ansible.cfg
On tor, 2016-04-28 at 08:54 -0700, johhue wrote:
> Is there a way to overrride where this "cp" directory goes?
Put something like this in your ansible.cfg.
[ssh_connection]
control_path = /path/to/new_cp/ansible-ssh-%%h-%%p-%%r
See also
On sön, 2016-04-24 at 12:00 -0700, Peter Loron wrote:
> I'm trying to provision a Ubuntu 16.04 server machine. When running
> a playbook which has worked fine on Ubuntu 14.x and 15.x, it fails
> with this error:
> ...
> Ubuntu 16.04 has python3, not 2.7.x. Why is this not being
> autodetected?
No
lör 2016-03-19 klockan 05:51 -0700 skrev George Khan:
> I ask it jan 18, and ask after 2 month: Any news about ansible2 in
> debian8/centos7 _stable_ repo? :)
I wouldn't keep my hopes up about seeing ansible 2.x in the regular
Jessie repositories. That because of Debian's general policy about
25 matches
Mail list logo
