[Gluster-users] gdeploy, Centos7 & Ansible 2.3

[hvjunk]

> On 09 May 2017, at 09:15 , Sachidananda URS <surs at redhat.com> wrote:
> 
> Hi,
> 
> On Mon, May 8, 2017 at 2:05 PM, hvjunk <hvjunk at gmail.com <mailto:hvjunk at gmail.com>> wrote:
> 
> <quote>
> 
> [root at linked-clone-of-centos-linux ~]# gdeploy -c t.conf
> 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/tmpvhTM5i/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
> 
> 
> That is strange. Can you please give me the following output?
> 
> $ rpm -qa | grep deploy
> $ rpm -qa | grep ansible

[root at linked-clone-of-centos-linux ~]# rpm -qa | egrep "deploy|ansible"
gdeploy-2.0.2-6.noarch
ansible-2.3.0.0-3.el7.noarch

> 
> Because after your mail tested on my machine and things seem to be working. So, I'm guessing
> there could be very trivial setup/package issues here which is causing this.
> 
> Once you confirm that you are using gdeploy-2.0.2-6 and ansible-2.2 or higher. Can you please
> perform the below steps to narrow down the error.
> 
> Maybe you can just trim your config file to contain just:
> 
> [hosts]
> 10.10.10.11
> 10.10.10.12
> 10.10.10.13
> 
> [backend-setup]
> devices=/dev/sdb
> mountpoints=/gluster/brick1
> brick_dirs=/gluster/brick1/one
> pools=pool1
> 
> And run the command:
> 
> $ gdeploy -c t.conf -k

[root at 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

> 
> The -k will ensure that your playbook temporary directory is not deleted.
> You see a message like:
> 
> You can view the generated configuration files inside /tmp/tmp...
> 
> Please cd to that directory and run:
> 
> $ ansible-playbook -i ansible_hosts pvcreate.yml
> 

[root at linked-clone-of-centos-linux ~]# cd /tmp/tmpGK2Arn
[root at 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 at linked-clone-of-centos-linux tmpGK2Arn]#

> Can you please let me know the results? We may have to take a closer look at your setup.
> 
> -sac
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170509/6da03093/attachment.html>