>>
>> On Sun, Apr 26, 2020, 22:10 Dick Visser >
>> wrote:
>>
>>> Which training is this?
>>> Usually with a training you need to come up with answers to questions
>>> yourself, and the trainer shows you the answer if you don't know it.
what is your actual
> intention? A group, a host, or...? This is necessary to answer your
> question.
>
> BTW attaching screendumps add unnecessary clutter for people and make it
> difficult for content to be indexed. So don't use screendumps but just
> text.
>
Please refer to the attached file for issues I am running into...
*Here is my playbook:*
--- # Ansible facts example
- hosts: centos
tasks:
- name: create a file to write the fact values
lineinfile:
path: /home/ansible/hostname
create: yes
line:
Ansible Control Machine (ip = 1.1.1.1):
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
Target Node (ip = 2.2.2.2):
NAME="Amazon Linux"
VERSION="2"
I am able to ssh from Ansible Control Machine to Target node if I manually
type the SSH commands (Which means the keys from Ansible Control
Thankyou Karl and Jonathan.
The issue is now resolved. It was issue with missing permissions of the
role associated to perform these actions.
On Thursday, 6 September 2018 22:05:26 UTC-7, Pravin Patil wrote:
>
> I am creating a playbook to create a EFS in AWS, using Ansible, but
> run
I am trying to automate the EFS creation and Mount it, using Ansible
playbook, but not sure how to pass the mount_point to another playbook.
In my Ansible Tower workflow, the first job creates EFS in AWS and then on
successful completion of this job, the Mount_point (of newly cerated EFS)
shoul
I am creating a playbook to create a EFS in AWS, using Ansible, but running
into errors.
Please suggest how to resolve this error.
*Below is my ansible script:*
---
- hosts: localhost
vars:
efs_name: "{{efs_name}}"
efs_tagname: "{{efs_tagname}}"
efs_purpose: "{{efs_purpose}}"
su
