Sachidananda Urs

@kristvanbesien can you attach your variable file? We pick the vdo_devs from the volume groups defined. So the role would try to mount the device only if /dev/mapper is defined...

@papanito firstly, I'm sorry I missed this. I'm thinking this could be lvol module limitation, they expect only int. Can you please provide something like 163G and check.

> Can we move validations to a pre-checks folder? @sabose I have answered this in the above comment: | Yes, it's possible as cache setup is optional @sabose I'm sorry...

Under thinpool and thinvolume create if you don't give size 100% will be assumed. roles/backend_setup/tasks/thin_pool_create.yml: size: "{{ item.thinpoolsize | default('100%FREE') }}" Leave out the thinpoolsize parameter. It will use the...

You are right regarding the consistency. But poolmetadata size we cannot leave it to default to 100%. Since it is just the metadata. And we have to default to a...

@sabose right. The role continued successfully till it reached thinpools. This is one of the enhancements I'm looking forward doing. (Idea picked from openshift-ansible) where we do a pre-check to...

It was idempotent earlier, but the commit https://github.com/gluster/gluster-ansible-infra/commit/0c1f454d98 changed that. But I do not see in the commit message why it was changed.

I don't think you should spend time on the PR. The committer should revert his changes unless he has a good reason. We can ask the maintainers to take a...

Michael I haven’t gotten time to look into it closely. Will check.

> Hi, I try to deploy glusterfs in raw machines but I got: > > ``` > TASK [gluster.cluster/roles/gluster_volume : Start glusterd on the nodes if not already started] *************************************************************************************************************************************************************...