<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 09 May 2017, at 09:15 , Sachidananda URS <<a href="mailto:surs@redhat.com" class="">surs@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<br class=""><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, May 8, 2017 at 2:05 PM, hvjunk <span dir="ltr" class=""><<a href="mailto:hvjunk@gmail.com" target="_blank" class="">hvjunk@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class=""><div style="overflow-wrap: break-word;" class=""><span class="gmail-"></span><quote><div class=""><br class=""></div><div class=""><span class="gmail-"><div class="">[root@linked-clone-of-centos-<wbr class="">linux ~]# gdeploy -c t.conf</div><div class="">ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.</div><div class=""><br class=""></div></span><div class="">The error appears to have been in '/tmp/tmpvhTM5i/pvcreate.yml': line 16, column 5, but may</div><span class="gmail-"><div class="">be elsewhere in the file depending on the exact syntax problem.</div><div class=""><br class=""></div><div class="">The offending line appears to be:</div><div class=""><br class=""></div><div class=""> # Create pv on all the disks</div><div class=""> - name: Create Physical Volume</div><div class=""> ^ here</div><div class=""><br class=""></div></span></div></div></blockquote><br class=""></div><div class="gmail_quote">That is strange. Can you please give me the following output?<br class=""><br class=""></div><div class="gmail_quote">$ rpm -qa | grep deploy<br class=""></div><div class="gmail_quote">$ rpm -qa | grep ansible<br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div>[root@linked-clone-of-centos-linux ~]# rpm -qa | egrep "deploy|ansible"</div><div>gdeploy-2.0.2-6.noarch</div><div>ansible-2.3.0.0-3.el7.noarch</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><br class=""></div><div class="gmail_quote">Because after your mail tested on my machine and things seem to be working. So, I'm guessing<br class=""></div><div class="gmail_quote">there could be very trivial setup/package issues here which is causing this.<br class=""><br class=""></div><div class="gmail_quote">Once you confirm that you are using gdeploy-2.0.2-6 and ansible-2.2 or higher. Can you please<br class=""></div><div class="gmail_quote">perform the below steps to narrow down the error.<br class=""><br class=""></div><div class="gmail_quote">Maybe you can just trim your config file to contain just:<br class=""><br class=""><span class="gmail-im"><div class="">[hosts]</div><div class="">10.10.10.11</div><div class="">10.10.10.12</div><div class="">10.10.10.13</div><div class=""><br class=""></div><div class="">[backend-setup]</div><div class="">devices=/dev/sdb</div><div class="">mountpoints=/gluster/brick1</div><div class="">brick_dirs=/gluster/brick1/one</div></span><div class="">pools=pool1<br class=""><br class=""></div><div class="">And run the command:<br class=""><br class=""></div><div class="">$ gdeploy -c t.conf -k<br class=""></div></div></div></div></div></div></blockquote><div><br class=""></div><div><div>[root@linked-clone-of-centos-linux ~]# gdeploy -c t.conf -k</div><div>ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.</div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> # Create pv on all the disks</div><div> - name: Create Physical Volume</div><div> ^ here</div><div><br class=""></div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> # Create pv on all the disks</div><div> - name: Create Physical Volume</div><div> ^ here</div><div><br class=""></div><div>Ignoring errors...</div><div>ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.</div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/vgcreate.yml': line 8, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> tasks:</div><div> - name: Create volume group on the disks</div><div> ^ here</div><div><br class=""></div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/vgcreate.yml': line 8, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> tasks:</div><div> - name: Create volume group on the disks</div><div> ^ here</div><div><br class=""></div><div>Ignoring errors...</div><div>ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.</div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/auto_lvcreate_for_gluster.yml': line 7, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> tasks:</div><div> - name: Create logical volume named metadata</div><div> ^ here</div><div><br class=""></div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/auto_lvcreate_for_gluster.yml': line 7, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> tasks:</div><div> - name: Create logical volume named metadata</div><div> ^ here</div><div><br class=""></div><div>Ignoring errors...</div><div><br class=""></div><div>PLAY [gluster_servers] *************************************************************************************</div><div><br class=""></div><div>TASK [Create an xfs filesystem] ****************************************************************************</div><div>failed: [10.10.10.11] (item=/dev/GLUSTER_vg1/GLUSTER_lv1) => {"failed": true, "item": "/dev/GLUSTER_vg1/GLUSTER_lv1", "msg": "Device /dev/GLUSTER_vg1/GLUSTER_lv1 not found."}</div><div>failed: [10.10.10.13] (item=/dev/GLUSTER_vg1/GLUSTER_lv1) => {"failed": true, "item": "/dev/GLUSTER_vg1/GLUSTER_lv1", "msg": "Device /dev/GLUSTER_vg1/GLUSTER_lv1 not found."}</div><div>failed: [10.10.10.12] (item=/dev/GLUSTER_vg1/GLUSTER_lv1) => {"failed": true, "item": "/dev/GLUSTER_vg1/GLUSTER_lv1", "msg": "Device /dev/GLUSTER_vg1/GLUSTER_lv1 not found."}</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>to retry, use: --limit @/tmp/tmpGK2Arn/fscreate.retry</div><div><br class=""></div><div>PLAY RECAP *************************************************************************************************</div><div>10.10.10.11 : ok=0 changed=0 unreachable=0 failed=1</div><div>10.10.10.12 : ok=0 changed=0 unreachable=0 failed=1</div><div>10.10.10.13 : ok=0 changed=0 unreachable=0 failed=1</div><div><br class=""></div><div>Ignoring errors...</div><div><br class=""></div><div>PLAY [gluster_servers] *************************************************************************************</div><div><br class=""></div><div>TASK [Create the backend disks, skips if present] **********************************************************</div><div>changed: [10.10.10.11] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div>changed: [10.10.10.13] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div>changed: [10.10.10.12] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div><br class=""></div><div>TASK [Mount the volumes] ***********************************************************************************</div><div>failed: [10.10.10.11] (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) => {"failed": true, "item": {"device": "/dev/GLUSTER_vg1/GLUSTER_lv1", "path": "/gluster/brick1"}, "msg": "Error mounting /gluster/brick1: mount: special device /dev/GLUSTER_vg1/GLUSTER_lv1 does not exist\n"}</div><div>failed: [10.10.10.13] (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) => {"failed": true, "item": {"device": "/dev/GLUSTER_vg1/GLUSTER_lv1", "path": "/gluster/brick1"}, "msg": "Error mounting /gluster/brick1: mount: special device /dev/GLUSTER_vg1/GLUSTER_lv1 does not exist\n"}</div><div>failed: [10.10.10.12] (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) => {"failed": true, "item": {"device": "/dev/GLUSTER_vg1/GLUSTER_lv1", "path": "/gluster/brick1"}, "msg": "Error mounting /gluster/brick1: mount: special device /dev/GLUSTER_vg1/GLUSTER_lv1 does not exist\n"}</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>to retry, use: --limit @/tmp/tmpGK2Arn/mount.retry</div><div><br class=""></div><div>PLAY RECAP *************************************************************************************************</div><div>10.10.10.11 : ok=1 changed=1 unreachable=0 failed=1</div><div>10.10.10.12 : ok=1 changed=1 unreachable=0 failed=1</div><div>10.10.10.13 : ok=1 changed=1 unreachable=0 failed=1</div><div><br class=""></div><div>Ignoring errors...</div><div><br class=""></div><div>PLAY [gluster_servers] *************************************************************************************</div><div><br class=""></div><div>TASK [Set SELinux labels on the bricks] ********************************************************************</div><div>changed: [10.10.10.11] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div>changed: [10.10.10.12] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div>changed: [10.10.10.13] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div><br class=""></div><div>TASK [Restore the SELinux context] *************************************************************************</div><div>changed: [10.10.10.12] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div>changed: [10.10.10.13] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div>changed: [10.10.10.11] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'})</div><div><br class=""></div><div>PLAY RECAP *************************************************************************************************</div><div>10.10.10.11 : ok=2 changed=2 unreachable=0 failed=0</div><div>10.10.10.12 : ok=2 changed=2 unreachable=0 failed=0</div><div>10.10.10.13 : ok=2 changed=2 unreachable=0 failed=0</div><div><br class=""></div><div>Error: No sections found in config file. Exiting!</div><div>You can view the generated configuration files inside /tmp/tmpGK2Arn</div></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class="">The -k will ensure that your playbook temporary directory is not deleted.<br class=""></div><div class="">You see a message like:<br class=""><br class="">You can view the generated configuration files inside /tmp/tmp...<br class=""><br class=""></div><div class="">Please cd to that directory and run:<br class=""><br class=""></div><div class="">$ ansible-playbook -i ansible_hosts pvcreate.yml<br class=""><br class=""></div></div></div></div></div></div></blockquote><div><br class=""></div><div><div>[root@linked-clone-of-centos-linux ~]# cd /tmp/tmpGK2Arn</div><div>[root@linked-clone-of-centos-linux tmpGK2Arn]# ansible-playbook -i ansible_hosts pvcreate.yml</div><div>ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.</div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> # Create pv on all the disks</div><div> - name: Create Physical Volume</div><div> ^ here</div><div><br class=""></div><div><br class=""></div><div>The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may</div><div>be elsewhere in the file depending on the exact syntax problem.</div><div><br class=""></div><div>The offending line appears to be:</div><div><br class=""></div><div> # Create pv on all the disks</div><div> - name: Create Physical Volume</div><div> ^ here</div><div><br class=""></div><div>[root@linked-clone-of-centos-linux tmpGK2Arn]#</div></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">Can you please let me know the results? We may have to take a closer look at your setup.<br class=""><br class=""></div><div class="">-sac<br class=""></div><div class=""><br class=""></div></div><div class="gmail_quote"><br class=""></div></div></div></div>
</div></blockquote></div><br class=""></body></html>