[ansible-project] Mahalakshmi HD digital set top box Kurnool | Mahalakshmidigital

[image: MLC.jpg] *Mahalakshmi digital set-top box offers great picture quality, incredibly vivid colors, sharper images, and stunning surround sound, MLC HD takes TV viewing to a whole new level.* *Visit for more Info: http://mahalakshmidigital.com/

[ansible-project] setting variable in a playbook from a jinjia2 snippet

Hi all is it possible assign variable built from jingia2 fragment to other variable in the playbook: - name: "list files in an archive" unarchive: src: /root/mybundle.zip dest: /opt list_files: yes remote_src: yes register: archive_content loop: - /root

[ansible-project] Re: setting variable in a playbook from a jinjia2 snippet

Sorry for the stupid question solved with - name: "debug archive_content" debug: var: path vars: path: "{% set output = [] %}\ {% for file in item.files %}\ {% if file | regex_search('.rpm$') %} {{ output.append(item.dest ~ '/'

[ansible-project] ansible error fpr sudo user

Hello Experts, I had a working playbook in my test environment, where my user was root user itslef and didnt have any issue. When i moved my playbook to staging environment , there my login user account is "admin" which is sudo user. But all of my playbooks are failing in this environment. ---

Re: [ansible-project] ansible error fpr sudo user

On 22/02/19 6:58 PM, visar wrote: Hello Experts, I had a working playbook in my test environment, where my user was root user itslef and didnt have any issue. When i moved my playbook to staging environment , there my login user account is "admin" which is sudo user. But all of my playbooks ar

Re: [ansible-project] ansible error fpr sudo user

Hello Sudeer.. No luck. --- - name: Replace the silent-install-server_ file to each Application Servers hosts: localhost,CCM,RM become: true vars: jts_file: /etc/ansible/roles/IBM2/files/silent-install-server_JTS.xml ccm_file: /etc/ansible/roles/IBM2/files/silent-install-server_CCM

Re: [ansible-project] ansible error fpr sudo user

On 22/02/19 7:19 PM, visar wrote: Hello Sudeer.. No luck. Logon to the server manually as admin and try doing something like `sudo ls`.  See if password is required on the server. - Sudheer | --- - name: Replace the silent-install-server_ file to each Application Servers hosts: localh

Re: [ansible-project] ansible error fpr sudo user

Hello Sudheer, Yes, Password required for any action . because my user "admin" is created and added to sudoers group in staging environment where the playbook is failing. Whereas in my development environment the playbook was working as there i jhad root user password. On Friday, February 22

[ansible-project] Re: ansible error fpr sudo user

Have you tried the -K flag? Try ansible-playbook -K yourplaybook.yaml -- Georg Großmann -- 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+uns

[ansible-project] Re: ansible error fpr sudo user

Hello Georg, Yes, tried. Please find the error below. ansible-playbook silentiInstallerfile1.yml -k SSH password: PLAY [Replace the silent-install-server_ file to each Application Servers] ** TASK [Gathering Facts

Re: [ansible-project] ansible error fpr sudo user

it looks like it needs a password to escalate, have a look at https://docs.ansible.com/ansible/latest/user_guide/become.html#connection-variables to set an escalation password. On Fri, 22 Feb 2019 at 13:50, visar wrote: > Hello Sudeer.. No luck. > > > --- > > - name: Replace the silent-install-s

Re: [ansible-project] ansible error fpr sudo user

On 22/02/19 7:29 PM, visar wrote: Hello Sudheer, Yes, Password required for any action . because my user "admin" is created and added to sudoers group in staging environment where the playbook is failing.  Whereas in my development environment the playbook was working as there i jhad root

Re: [ansible-project] ansible error fpr sudo user

Hello sudeer, Yes. I had added the user admin to sudoers and made password less as same as given for root user in the sudoers file. But still no luck On Fri, 22 Feb 2019, 19:49 Sudheer S, wrote: > > On 22/02/19 7:29 PM, visar wrote: > > Hello Sudheer, > > Yes, Password required for any action

Re: [ansible-project] ansible error fpr sudo user

Hello kief, I already tried with different options of become as given in the link But couldn't resolve . I am not sure that which part of the playbook which I need to modify inorder to make it run for admin user. Where this playbook is working fine in another environmental where using root user

Re: [ansible-project] ansible error fpr sudo user

On 22/02/19 8:16 PM, vivek vijayan wrote: Hello sudeer, Yes. I had added the user admin to sudoers and made password less as same as given for  root user in the sudoers file. But still no luck I would first make sure that sudoer configuration is correct on the target server. So, logon to

Re: [ansible-project] ansible error fpr sudo user

> But couldn't resolve . I am not sure that which part of the playbook which I need to modify inorder to make it run for admin user. I've been doing a lot of become work the last day, I found it's designed to work on a task level in roles but does this work? - name: Replace the silent-install-se

Re: [ansible-project] ansible error fpr sudo user

Hello Sudheer, Verified in all the servers and this was enabled already. ## Allow root to run any commands anywhere root ALL=(ALL) NOPASSWD: ALL admin ALL=(ALL) NOPASSWD: ALL On Friday, February 22, 2019 at 8:20:35 PM UTC+5:30, Sudheer S wrote: > > > On 22/02/19 8:16 PM, vivek vijayan wrote: >

Re: [ansible-project] ansible error fpr sudo user

ansible-playbook -k silentiInstallerfile1.yml SSH password: ERROR! 'ansible_become_user' is not a valid attribute for a Play The error appears to have been in '/etc/ansible/roles/IBM2/tasks/best/silentiInstallerfile1.yml': line 3, column 3, but may be elsewhere in the file depending on the exact

Re: [ansible-project] network-engine - parser problem

On Fri, Feb 22, 2019 at 10:57 AM 'Andreas Bourges' via Ansible Project wrote: > > Hi, > > ...I'm currently having a look at network-engine and so far it looks really > promising! Seems like the best solution for network automation there is today > :-) However, I'm having trouble parsing a certai

AW: [ansible-project] network-engine - parser problem

Hi Trishna, > You might want to use `match_all: yes` which doesn't stop on your first > match. > > - name: trunk allowed vlan > pattern_match: > regex: " switchport trunk allowed vlan (.*)" > content: "{{ item }}" > match_all: yes > register: allowed_vlans > Thanks for your rep

[ansible-project] win_package and check_mode

Hello, I have a question about running win_package in check_mode. My playbook (part of it): - name: Copy Splunk Forwarder MSI win_copy: src: "{{ splunk_forwarder_distro }}" dest: "{{ splunk_forwarder_distro_local }}" force: yes remote_src: no - name: Install Splunk Fo

[ansible-project] Re: mangling include_role path

my current workaround is to stash top-level playbook's directory and use "include_tasks" instead of "include_role": main.yml === - hosts: all tasks: - set_fact: top_pb_dir="{{ playbook_dir }}" - include_playbook: a/b/c/foo.yml a/b/c/foo.yml == - include_tasks: "{{ top_pb_dir

Re: [ansible-project] ansible error fpr sudo user

On 22/02/19 8:16 PM, vivek vijayan wrote: Hello sudeer, Yes. I had added the user admin to sudoers and made password less as same as given for  root user in the sudoers file. But still no luck Are you both representing the same organization and hence the same problem? I am confused by mul

Re: [ansible-project] Dropping Fedora rpms from https://releases.ansible.com/

On Mon, Feb 18, 2019 at 7:45 PM Toshio Kuratomi wrote: > > Hey all, > > Recently we had a discussion internally about whether to build > upstream Ansible rpms on Fedora 29 using Python3 or Python2. This > lead to a question about how useful the Fedora rpms Ansible releases > on https://releases.a

Re: [ansible-project] ansible error fpr sudo user

One more point to verify : Are you connected with admin user on the controller-server (where you play your playbook) ? If not you should use remote_user to admin... Perhaps a verbose log error could help use - when playing ansible-playbook Regards, JYL Le 22/02/2019 à 14:28, visa

[ansible-project] error run shell script for start service jboss

PLAYBOOK: - hosts: all gather_facts: yes remote_user: root become: yes tasks: - name: Inicializa Servicio JBOSS 1.1 shell: sh /home/jboss/jboss-6.4/bin/standalone.sh ignore_errors: yes - name: Inicializa Servicio JBOSS 1.2 command: sh /home/jboss/jboss-6.4/bin/standalone.sh ignore_errors: yes deleg

Re: [ansible-project] error run shell script for start service jboss

I see a lot of "trial and error" attempts with command/shell, and with errors ignored. If I had to guess, those shell scripts rely on a number of environment variables that aren't available to ansible. This is a good start: https://docs.ansible.com/ansible/latest/user_guide/playbooks_environment.h

[ansible-project] Ansible Failed Authentication

I am starting out at ansible with a basic playbook to learn ansible I am getting the error message below I know the user and creds are correct I have logged into that switch from ansible server can someone please let me know what I am missing? #error message TASK [Gathering Facts] **

[ansible-project] why i cannot remove this file /etc/yum.repos.d/redhat-rhui,repo even with the root permission.

Dear Ansible Gurus and friends: I have the following ansible script to remove the default AWS repos on an new created RHEL ec2 instance from Packer. It works well untill the "Remove AWS RHUI repos" module. For some reason, the privilege escalation doesn't work for this native file module. Howe

[ansible-project] Re: why i cannot remove this file /etc/yum.repos.d/redhat-rhui,repo even with the root permission.

Here is the output with --vvv option: amazon-ebs: TASK [Remove AWS RHUI repos] *** amazon-ebs: failed: [default] (item=/etc/yum.repos.d/redhat-rhui.repo) => {"changed": false, "gid": 0, "group": "root", "item": "/etc/yum.repos.d/redhat-rhu

Re: [ansible-project] Re: why i cannot remove this file /etc/yum.repos.d/redhat-rhui,repo even with the root permission.

*I got it reoslved by using a different user. running packer under root will not escalate the privilege to root. not sure if it's a bug or something. * On Fri, Feb 22, 2019 at 3:37 PM Jason Yu wrote: > Here is the output with --vvv option: > > >amazon-ebs: TASK [Remove AWS RHUI repos] >