I am glad you got this working. I have to prepare for this same setup and
wondering if you have any comprehensive notes that you can share here?
On Wednesday, February 3, 2016 at 6:24:20 PM UTC-5, Nikhil Shah wrote:
>
> I'd like to thank you all, i was able to resolve my windows issue. Few
>
I have a playbook that installs the appropriate packages for Active
Directory Authentication. When it gets to the "join" portion, Ansible just
sits there because the join process is asking the user for the password of
the account that has access to join the system to Active Directory. How can
I have a playbook that installs the appropriate packages for Active
Directory Authentication. When it gets to the "join" portion, Ansible just
sits there because the join process is asking the user for the password of
the account that has access to join the system to Active Directory. How can
Hi Mike,
When I say "moved it up one level", I meant I took my hosts file out of the
roles directory and moved it up one level out of there.
Now, back to your suggestions. For your first point, I am not sure I
follow. For example, you said to run my play (I understand this as task)
with
I am creating a role to install some packages and then join a system to a
domain controller. However, when I run my playbook, it comes back saying
*ERROR!
ERROR! 'test' is undefined.* Here is how I am running my playbook:
ansible-playbook -i server_hosts app_install_main.yml
I don't see
I am creating a role with *ansible-galaxy init role_name*. One of the tasks
in that role will be to install_app.yml and another to remove_app.yml (one
to install and one to remove). Is it possible to call one task vs the other
within that role or do I need to create a whole new role for that
I have a couple of systems that follow a strict hostname schema. For
example, depending on the environment, they all follow the same prefix for
that environment:
- For development = dev-server1.domain.tld
- For testing = test-server1.domain.tld
- For production =
718.404.6429 | ansible.com <https://www.ansible.com/>
>
> GitHub: tima <https://www.github.com/tima>
>
> Twitter: @appnelgroup <https://www.twitter.com/@appnelgroup>
>
> On Mon, Mar 14, 2016 at 4:24 PM, Gilberto Valentin <gvale...@gmail.co
4.6429 | ansible.com <https://www.ansible.com/>
>
> GitHub: tima <https://www.github.com/tima>
>
> Twitter: @appnelgroup <https://www.twitter.com/@appnelgroup>
>
> On Mon, Mar 14, 2016 at 4:42 PM, Gilberto Valentin <gvale...@gmail.com
> > wro
Mike and Uditha,
Ok, I see what you guys are saying about the hosts. I moved it one level up
and now we are getting somewhere. Now, the issue is that it can't run my
task because it doesn't see the value of my conditional. For example, I
want my task to run *when: "{{ testserver }}"*. In other
Hi Arthur,
Actually, I do have my app_install as a sub directory under roles. It's
just that initially I only pasted everything within roles and only showing
you that. Here's a better view:
~/git/ansible/roles$ tree
.
└── project1
├── server_hosts
├── app_install
│ ├── README.md
I can't put this up on github. I had to sanitize it a lot just to get it
here too :/.
If the structure is wrong, then I am not sure what should be changed. I got
that structure initially by running *ansible-galaxy init role_name* and
have modified the structure here and there based on
Mike,
I got a bit further with your suggestion. I changed my tree to look like
the one you have and now it looks like it's trying to kick. However, now
it's not finding the value of my *hosts: *"{{ test }}"
When I run the command, I see this now:
[WARNING]: provided hosts list is empty, only
Hi Mike,
Thanks for the suggestions. I tried to implement what you mentioned and I
ended up breaking everything. I am completely lost with this. I am just
going to have to start over at this point. Between sanitizing the data to
post here and then trying to translate your suggestions back to
Mike,
Thanks for your patience and assistance. I wanted to do it the way you
suggested so that I get in the habit of crafting my roles that can be
useful in other ways later. With that said, I think I am getting the hang
of what you are saying. I started completely over and separated my roles.
I have a task that calls a root password from my vault.yml by adding it to
the task as:
vars:
ansible_become_pass:"{{ root }}"
However, I have to use it multiple times within my tasks/main.yml. Is is
possible to add that variable once to vars/main.yml
Here is what my tasks/main.yml looks
OK, I figured this out. I added the following to my site.yml:
- name: install app to all test servers
hosts: testservers
become: yes
user: service_account
vars_files:
- vault.yml
vars:
ansible_become_pass: "{{ root }}"
roles:
- pb_install_test
--
You received this
Mike,
So the roles directory is something I created manually. I saw this on a
video tutorial directly made from Ansible and the instructor was creating
these manually and then initiating the roles from within the roles
directly. I applied the same concept and it worked :). I'll def. check out
Hi Arthur, can you elaborate on exporting ANSIBLE_INVENTORY? All I did was
call my inventory file like this: *ansible-playbook -i server_hosts
app_install_main.yml*
Thanks for the quick response :)
On Thursday, March 17, 2016 at 8:26:17 PM UTC-4, Arthur Reyes wrote:
>
> Just a thought. Did you
Mike,
And then in my app_install_main.yml, I have the following:
---
- name: install app and join systems to domain
hosts: "{{ test }}"
become: yes
roles:
- app_install
vars_prompt:
- name: "ansible_sudo_pass"
prompt: "Sudo password"
private: yes
--
You received this
le at all
On Friday, March 18, 2016 at 8:03:05 AM UTC-4, Gilberto Valentin wrote:
>
> Hi Arthur,
>
> Actually, I do have my app_install as a sub directory under roles. It's
> just that initially I only pasted everything within roles and only showing
> you that. Here's a bett
rsed": false}
NO MORE HOSTS LEFT
*
to retry, use: --limit @adAuth_asRoot.retry
PLAY RECAP
*****
ansible: ok=2changed=1unreachable=0failed=1
On Monday,
how to encrypt the password.
On Monday, February 29, 2016 at 10:43:08 PM UTC-5, Gilberto Valentin wrote:
>
> I have a playbook that installs the appropriate packages for Active
> Directory Authentication. When it gets to the "join" portion, Ansible just
> sits there because the join
I currently have a playbook (not completed) that installs some packages and
sets up MySQL. I have one task that notifies several handlers if that task
is changed. However, one of the handler tasks, which uses the 'expect'
module, fails. The task first installs mysqld if necessary. If it
I wanted to point out that I noticed my issue was a bug per
https://github.com/ansible/ansible/issues/15572
However, I grabbed the latest version of Ansible, which is 2.2 and still
have the same issue. The problem is that my handler fails and doesn't
complete the last question/response in
I am having a similar or maybe not so similar issue. If I get a response on
my thread on how to work out my issue or if I figure it out, I'll let you
know. Here is my thread so you can see how I am using the *failed_when: *
option
I need to use single quotes here because 'Can't drop database' is the
failure I am filtering *in result.stdout*
On Friday, May 13, 2016 at 4:17:13 PM UTC-4, Johannes Kastl wrote:
>
> On 12.05.16 15:55 Gilberto Valentin wrote:
>
> > register: result
> > failed_when:
So I already have *ignore_errors: yes *set. What I am trying to figure out
is why my response on my handler is failing. So here is my handler:
- name: Secure MySQL Installation
register: result
failed_when: "Can't drop database in result.stdout"
ignore_errors: yes
expect:
Anyone out there with any idea on this issue?
--
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...@googlegroups.com.
To post to this
Just checking in to see if anyone has ever ran into this issue with this
external module.
On Friday, September 9, 2016 at 4:21:57 PM UTC-4, Gilberto Valentin wrote:
>
> I am trying to run *ntc_show_command *module but getting the following
> error:
>
> {"changed": fa
I am trying to run *ntc_show_command *module but getting the following
error:
{"changed": false, "failed": true, "msg": "This module requires TextFSM"}
Here is my pip list:
Babel (0.9.6)
> cffi (1.7.0)
> coverage (4.2)
> cryptography (1.5)
> docutils (0.11)
> enum34 (1.1.6)
> funcsigs (1.0.2)
Hello, I am interested in pulling specific data from a table/field and
apply that data to a .j2 template. For example, if I have a license key in
a table on a field called RedHat license, I want to pull that license value
and have my .j2 template use it for the creation of an XML template. I
Thanks for the info...I'll definitely try this out :)
On Friday, March 3, 2017 at 3:03:33 PM UTC-5, Kai Stian Olstad wrote:
>
> On 03. mars 2017 19:51, Gilberto Valentin wrote:
> > Hello, I am interested in pulling specific data from a table/field and
> > apply that data
I am curious to see what you are all doing to do DB dumps of MSSQL schema's
using Ansible. Looking at the *mssql_db* module, the only option I see is
for importing. What is everyone else doing to get some backups via Ansible?
--
You received this message because you are subscribed to the
Hello,
I have a playbook that scans for hard drives and mounts them in order to do
a backup of the data from those drives. I am able to scan for the drives
just fine and I can also mount them (thanks to the Ansible IRC community).
The only issue I am having is mounting ONLY when the partition
Any suggestions? :)
On Tuesday, July 25, 2017 at 8:42:25 AM UTC-4, Gilberto Valentin wrote:
>
> Hello,
>
> I have a playbook that scans for hard drives and mounts them in order to
> do a backup of the data from those drives. I am able to scan for the drives
> just fine and I c
hat I want and that would be
filtering through partitions that are NTFS only. An example, if you have
one, would be great. I am still lost on how to only list out and mount
partitions that are NTFS only
On Thursday, July 27, 2017 at 1:00:14 PM UTC-4, Kai Stian Olstad wrote:
>
> On 27. juli 2017
ating conditional (item.partitions | length > 0
> and item.partitions | selectattr('fstype', 'equalto', 'ntfs') | list |
> length > 0): 'dict object' has no attribute 'partitions'\n\nThe error
> appears to have been in
> '/home/svcacctansible/automation/backup/customerBackup.yml': line 35,
> column 7, but may\nbe elsewhere in the file depending on the exact syntax
> problem.\n\nThe offending line appears to be:\n\n\n- name: mount ntfs
> partitions\n
I have the following playbook:
---
## Tasks for software install
- name: Java 1.8
yum: name={{ item }} state=installed
with_items:
- java-1.8.0-openjdk-devel
- name: Guest groups
group:
name: '{{ guest_user_group }}'
gid: '{{ guest_user_group_gid }}'
- name: Default guest
With the help of members of the IRC #ansible channel, I was able to solve
my logic. What I ended up doing was removing the following task:
- name: Enable and start app
systemd:
name: guest
enabled: yes
state: started
daemon_reload: yes
Then, I modified the handler for *nofity:
40 matches
Mail list logo