<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Ansible (na_ontap_commands) Epic refresh script (eeod) fails intermittently in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Ansible-na-ontap-commands-Epic-refresh-script-eeod-fails-intermittently/m-p/439477#M41412</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using the Ansible (na_ontap_commands) Epic refresh script (eeod) and it has been failing intermittently.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our setup consist of vm running the Epic environments (both production as the source of the refresh as well as non-production as the destination of the refresh) as well as physical proxy servers (as the destination of the refresh for backup purposes; i.e. not running an environment).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issues we have seen are sometimes related to timing issues (getting unknown devices and just after the failure these unknowns are gone; getting /dev/sd* devices instead of /dev/mapper/... devices esp. for the physical proxy's) but also non-timing related issues (getting unknown devices that can't be solved by waiting - we solve this by removing the volume group to be able to rerun the script).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We already have made several changes to the script (together with Christian Bauernfeind of NetApp) to include sleep command's, increased logging etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are your experiences with this script and do you have pointers to improve the reliability?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jan-Pieter&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 09:56:07 GMT</pubDate>
    <dc:creator>Jan-PieterTevel</dc:creator>
    <dc:date>2025-06-04T09:56:07Z</dc:date>
    <item>
      <title>Ansible (na_ontap_commands) Epic refresh script (eeod) fails intermittently</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Ansible-na-ontap-commands-Epic-refresh-script-eeod-fails-intermittently/m-p/439477#M41412</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using the Ansible (na_ontap_commands) Epic refresh script (eeod) and it has been failing intermittently.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our setup consist of vm running the Epic environments (both production as the source of the refresh as well as non-production as the destination of the refresh) as well as physical proxy servers (as the destination of the refresh for backup purposes; i.e. not running an environment).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issues we have seen are sometimes related to timing issues (getting unknown devices and just after the failure these unknowns are gone; getting /dev/sd* devices instead of /dev/mapper/... devices esp. for the physical proxy's) but also non-timing related issues (getting unknown devices that can't be solved by waiting - we solve this by removing the volume group to be able to rerun the script).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We already have made several changes to the script (together with Christian Bauernfeind of NetApp) to include sleep command's, increased logging etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are your experiences with this script and do you have pointers to improve the reliability?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jan-Pieter&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:56:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Ansible-na-ontap-commands-Epic-refresh-script-eeod-fails-intermittently/m-p/439477#M41412</guid>
      <dc:creator>Jan-PieterTevel</dc:creator>
      <dc:date>2025-06-04T09:56:07Z</dc:date>
    </item>
  </channel>
</rss>

