[root@linked-clone-of-centos-linux ~]# rpm -qa | egrep "deploy|ansible" gdeploy-2.0.2-6.noarch ansible-2.3.0.0-3.el7.noarch
[root@linked-clone-of-centos-linux ~]# gdeploy -c t.conf -k ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path. The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: # Create pv on all the disks - name: Create Physical Volume ^ here The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: # Create pv on all the disks - name: Create Physical Volume ^ here Ignoring errors... ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path. The error appears to have been in '/tmp/tmpGK2Arn/vgcreate.yml': line 8, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: tasks: - name: Create volume group on the disks ^ here The error appears to have been in '/tmp/tmpGK2Arn/vgcreate.yml': line 8, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: tasks: - name: Create volume group on the disks ^ here Ignoring errors... ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path. The error appears to have been in '/tmp/tmpGK2Arn/auto_lvcreate_for_gluster.yml': line 7, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: tasks: - name: Create logical volume named metadata ^ here The error appears to have been in '/tmp/tmpGK2Arn/auto_lvcreate_for_gluster.yml': line 7, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: tasks: - name: Create logical volume named metadata ^ here Ignoring errors... PLAY [gluster_servers] ************************************************************************************* TASK [Create an xfs filesystem] **************************************************************************** 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."} 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."} 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."} to retry, use: --limit @/tmp/tmpGK2Arn/fscreate.retry PLAY RECAP ************************************************************************************************* 10.10.10.11 : ok=0 changed=0 unreachable=0 failed=1 10.10.10.12 : ok=0 changed=0 unreachable=0 failed=1 10.10.10.13 : ok=0 changed=0 unreachable=0 failed=1 Ignoring errors... PLAY [gluster_servers] ************************************************************************************* TASK [Create the backend disks, skips if present] ********************************************************** changed: [10.10.10.11] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) changed: [10.10.10.13] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) changed: [10.10.10.12] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) TASK [Mount the volumes] *********************************************************************************** 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"} 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"} 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"} to retry, use: --limit @/tmp/tmpGK2Arn/mount.retry PLAY RECAP ************************************************************************************************* 10.10.10.11 : ok=1 changed=1 unreachable=0 failed=1 10.10.10.12 : ok=1 changed=1 unreachable=0 failed=1 10.10.10.13 : ok=1 changed=1 unreachable=0 failed=1 Ignoring errors... PLAY [gluster_servers] ************************************************************************************* TASK [Set SELinux labels on the bricks] ******************************************************************** changed: [10.10.10.11] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) changed: [10.10.10.12] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) changed: [10.10.10.13] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) TASK [Restore the SELinux context] ************************************************************************* changed: [10.10.10.12] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) changed: [10.10.10.13] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) changed: [10.10.10.11] => (item={u'device': u'/dev/GLUSTER_vg1/GLUSTER_lv1', u'path': u'/gluster/brick1'}) PLAY RECAP ************************************************************************************************* 10.10.10.11 : ok=2 changed=2 unreachable=0 failed=0 10.10.10.12 : ok=2 changed=2 unreachable=0 failed=0 10.10.10.13 : ok=2 changed=2 unreachable=0 failed=0 Error: No sections found in config file. Exiting! You can view the generated configuration files inside /tmp/tmpGK2Arn
[root@linked-clone-of-centos-linux ~]# cd /tmp/tmpGK2Arn [root@linked-clone-of-centos-linux tmpGK2Arn]# ansible-playbook -i ansible_hosts pvcreate.yml ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path. The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: # Create pv on all the disks - name: Create Physical Volume ^ here The error appears to have been in '/tmp/tmpGK2Arn/pvcreate.yml': line 16, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: # Create pv on all the disks - name: Create Physical Volume ^ here [root@linked-clone-of-centos-linux tmpGK2Arn]#
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
