So you solved.. 
The blank counts for the matching of the marker lines.. 

fusillator@catorcio:~/Code/ansible/test$ ansible-playbook blockinfile.yml 

PLAY [localhost] 
**************************************************************************************************************************************************************************************************************************************************************

TASK [Gathering Facts] 
********************************************************************************************************************************************************************************************************************************************************
ok: [localhost]

TASK [remove block regexps] 
***************************************************************************************************************************************************************************************************************************************************
changed: [localhost]

PLAY RECAP 
********************************************************************************************************************************************************************************************************************************************************************
localhost                  : ok=2    changed=1    unreachable=0    
failed=0   

fusillator@catorcio:~/Code/ansible/test$ cat resolv.conf
nameserver 8.8.8.8
fusillator@catorcio:~/Code/ansible/test$ cat resolv.conf
resolv.conf                            
resolv.conf.3339.2019-02-26@20:21:57~  
resolv.conf.3740.2019-02-27@11:09:34~  
resolv.conf.4381.2019-02-27@12:03:36~  
fusillator@catorcio:~/Code/ansible/test$ cat resolv.conf
resolv.conf                            
resolv.conf.3339.2019-02-26@20:21:57~  
resolv.conf.3740.2019-02-27@11:09:34~  
resolv.conf.4381.2019-02-27@12:03:36~  
fusillator@catorcio:~/Code/ansible/test$ cat 
resolv.conf.4381.2019-02-27@12\:03\:36~ 
nameserver 8.8.8.8
nameserver 13.2.7.8 #dns
nameserver 13.2.7.9
nameserver 13.2.7.10
search eu.ro.net mrtools.ro.com mit.gbr.ro.com
fusillator@catorcio:~/Code/ansible/test$ cat blockinfile.yml 
- hosts: localhost
  tasks:
  - name: remove block regexps
    blockinfile:
      path: "./resolv.conf"
      marker: "{mark}"
      marker_begin: "nameserver 13.2.7.8 #dns"
      marker_end: "search eu.ro.net mrtools.ro.com mit.gbr.ro.com"
      state: absent
      backup: yes

regards

Luca 


Il giorno mercoledì 27 febbraio 2019 11:59:05 UTC+1, Deepan M ha scritto:
>
> Hi Luca,
>
>  Perfectly working what you have suggested. 
>
> I need one more suggestion, below is the content i want remove but when 
> the line ends with #name its not working ? do you know how to remove with 
> that also?
>
> *Playbook:-*
>
>  cat resolve.yml
> ---
> - hosts: TC2
>   become: yes
>   tasks:
>   - name: remove block regexps
>     blockinfile:
>       path: /tmp/resolv.conf
>       marker: "{mark}"
>       marker_begin: "nameserver 13.2.7.8  # dns1"
>       block: |
>           nameserver 13.2.7.9   # dns2
>           nameserver 13.2.7.10  # dns3
>       marker_end: "search eu.ro.net mrtools.ro.com mit.gbr.ro.com"
>       state: absent
>       backup: yes
>
>
>
> *Client Side:-*
> # cat resolv.conf
> nameserver 13.2.7.8     # dns1
> nameserver 13.2.7.9     # dns2
> nameserver 13.2.7.10    # dns3
> search eu.ro.net mrtools.ro.com mit.gbr.ro.com
>
> Thanks,
> Deepan M
>
> On Wednesday, February 27, 2019 at 3:57:36 PM UTC+5:30, fusillator wrote:
>>
>> blockinfile is the right choice
>> anyway I'm not sure if the argument block is necessary
>>
>> fusillator@catorcio:~/Code/ansible/test$ cat resolv.conf
>> nameserver 8.8.8.8
>> nameserver 13.2.7.8
>> nameserver 13.2.7.9
>> nameserver 13.2.7.10
>> search eu.ro.net mrtools.ro.com mit.gbr.ro.com
>>
>> fusillator@catorcio:~/Code/ansible/test$ cat blockinfile.yml 
>> - hosts: localhost
>>   tasks:
>>   - name: remove block regexps
>>     blockinfile:
>>       path: "./resolv.conf"
>>       marker: "{mark}"
>>       marker_begin: "nameserver 13.2.7.8"
>>       marker_end: "search eu.ro.net mrtools.ro.com mit.gbr.ro.com"
>>       state: absent
>>       backup: yes
>>
>>
>> fusillator@catorcio:~/Code/ansible/test$ ansible-playbook blockinfile.yml 
>>
>> PLAY [localhost] 
>> **************************************************************************************************************************************************************************************************************************************************************
>>
>> TASK [Gathering Facts] 
>> ********************************************************************************************************************************************************************************************************************************************************
>> ok: [localhost]
>>
>> TASK [remove block regexps] 
>> ***************************************************************************************************************************************************************************************************************************************************
>> changed: [localhost]
>>
>> PLAY RECAP 
>> ********************************************************************************************************************************************************************************************************************************************************************
>> localhost                  : ok=2    changed=1    unreachable=0    
>> failed=0   
>>
>> fusillator@catorcio:~/Code/ansible/test$ cat resolv.conf
>> nameserver 8.8.8.8
>>
>> Can you launch the playbook with increased verbosity to analyze the 
>> failure? 
>> Maybe it could be useful the debug feature to shorten the test:
>>
>> https://docs.ansible.com/ansible/latest/user_guide/playbooks_debugger.html
>>
>> Unfortunatly at the moment I'm not on a rhel host. 
>> Try also to check audit log for selinux restrictions
>> sealert -a /var/log/audit.log
>>
>>
>> regards
>>
>> Luca 
>>
>>
>>
>>
>> Il giorno mercoledì 27 febbraio 2019 10:54:46 UTC+1, Deepan M ha scritto:
>>>
>>> Hello Luca,
>>>
>>>
>>> *Are you sure the problem is ansible?*
>>> :-Not Sure, same playbook is working on rhel6 but not in rhel7, means no 
>>> error.
>>>
>>> *the playbook fails? what's the shown message? *
>>>
>>> :-no, playbook is working successfully in rhel 6, but rhel 7 its 
>>> failing, not only resolv.conf even i tried with dummy file created on /tmp 
>>> however that also failed.
>>>
>>> *:-Or the problem is that the configuration are reset on reboot?*
>>>
>>> no configuration issue
>>>
>>> *Furthermore I don't get why you use the argument block with blockinfile 
>>> in order to remove the block.. isn't unnecessary?*
>>>
>>> :- is there any module did ansible is having it for removing block in 
>>> file ?
>>>
>>> Thanks,
>>> Deepan M
>>>
>>> On Wednesday, February 27, 2019 at 12:04:04 AM UTC+5:30, fusillator 
>>> wrote:
>>>>
>>>> take a look at /var/log/messages for line with 
>>>>
>>>> updated /etc/resolv.conf
>>>> see more details at https://access.redhat.com/solutions/7412
>>>>
>>>>
>>>> Il giorno martedì 26 febbraio 2019 19:23:25 UTC+1, fusillator ha 
>>>> scritto:
>>>>>
>>>>> Are you sure the problem is ansible?
>>>>> the playbook fails? what's the shown message? 
>>>>> Or the problem is that the configuration are reset on reboot?
>>>>>
>>>>> regards
>>>>>
>>>>> Luca
>>>>>
>>>>>
>>>>> Il giorno martedì 26 febbraio 2019 15:49:35 UTC+1, Deepan M ha scritto:
>>>>>>
>>>>>>
>>>>>> Hello Guys,
>>>>>>
>>>>>>  Can someone please help me to resolve this issue.
>>>>>>
>>>>>> below playbook i have created to remove dns entries from resolv.conf 
>>>>>> and its working perfect on rhel 6 but not in rhel 7.6, is there any bug 
>>>>>> or 
>>>>>> i need to add any parameters ?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Playbook :- blockinfile*
>>>>>> ---
>>>>>> - hosts: TC2
>>>>>>   become: yes
>>>>>>   tasks:
>>>>>>  - name: remove block regexps
>>>>>>     blockinfile:
>>>>>>       path: /etc/resolv.conf
>>>>>>       marker: "{mark}"
>>>>>>       marker_begin: "nameserver 13.2.7.8 "
>>>>>>       block: |
>>>>>>          nameserver 13.2.7.9  
>>>>>>          nameserver 13.2.7.10
>>>>>>       marker_end: "search eu.ro.net mrtools.ro.com mit.gbr.ro.com"
>>>>>>       state: absent
>>>>>>       backup: yes
>>>>>>
>>>>>> *Playbook :- lineinfile*
>>>>>> ---
>>>>>> - hosts: TC2
>>>>>>   become: yes
>>>>>>   tasks:
>>>>>>   - name: copy the file
>>>>>>     shell: cp -p /etc/resolv.conf /tmp/resolv.conf.$(date +%F_%R)
>>>>>>   - name: remove block lines
>>>>>>     lineinfile:
>>>>>>       dest: /etc/resolv.conf
>>>>>>       regexp: "{{ item.line }}"
>>>>>>       state: absent
>>>>>>     with_items:
>>>>>>       - { line: 'nameserver 13.2.7.8' }
>>>>>>       - { line: 'nameserver 13.2.7.9' }
>>>>>>       - { line: 'nameserver 13.2.7.10' }
>>>>>>       - { line: 'search eu.ro.net mrtools.ro.com mit.gbr.ro.com' }
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Client server:-*
>>>>>>
>>>>>> Hostname: testmachine
>>>>>>  Distro:   [redhat-release] Red Hat Enterprise Linux Server release 
>>>>>> 7.6 (Maipo)
>>>>>>            [os-release] Red Hat Enterprise Linux 7.6 (Maipo)
>>>>>> Booted kernel:  3.10.0-957.1.3.el7.x86_64
>>>>>>
>>>>>> *ansible control node:-*
>>>>>> ansible 2.7.7
>>>>>>   config file = /etc/ansible/ansible.cfg
>>>>>>   configured module search path = 
>>>>>> [u'/home/q5c9nf32/.ansible/plugins/modules', 
>>>>>> u'/usr/share/ansible/plugins/modules']
>>>>>>   ansible python module location = 
>>>>>> /usr/lib/python2.7/site-packages/ansible
>>>>>>   executable location = /usr/bin/ansible
>>>>>>   python version = 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 
>>>>>> 20150623 (Red Hat 4.8.5-36)]
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Deepan M
>>>>>>
>>>>>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/c8a6dca2-b4be-43c7-80d0-032cc220583e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to