I would recommend to do cleanup from cockpit or if you are using cli based
deployment then use
"/etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml"
with your inventory.
Then try to deploy again. Cleanup takes care everything.
On Thu, Apr 30, 2020 at 9:59
On April 30, 2020 12:31:59 PM GMT+03:00, Shareef Jalloq
wrote:
>Changing to /dev/mapper names seems to work but if anyone can tell me
>why
>the /dev/sd* naming is filtered that would help my understanding.
>
>On Thu, Apr 30, 2020 at 10:13 AM Shareef Jalloq
>wrote:
>
>> Having no luck here.
It's running now using the /dev/mapper/by-id name so I'll just stick with
that and use this in the future. Thanks.
On Thu, Apr 30, 2020 at 3:43 PM Strahil Nikolov
wrote:
> On April 29, 2020 8:21:58 PM GMT+03:00, Shareef Jalloq <
> shar...@jalloq.co.uk> wrote:
> >Actually, now I've fixed that,
On April 29, 2020 8:21:58 PM GMT+03:00, Shareef Jalloq
wrote:
>Actually, now I've fixed that, indeed, the deployment now fails with an
>lvm
>filter error. I'm not familiar with filters but there aren't any
>uncommented instances of 'filter' in /etc/lvm/lvm.conf.
>
>
>
>On Wed, Apr 29, 2020 at
On April 29, 2020 7:42:55 PM GMT+03:00, Shareef Jalloq
wrote:
>Ah of course. I was assuming something had gone wrong with the
>deployment
>and it couldn't clean up its own mess. I'll raise a bug on the
>documentation.
>
>Strahil, what are the other options to using /dev/sdxxx?
>
>On Wed, Apr
Changing to /dev/mapper names seems to work but if anyone can tell me why
the /dev/sd* naming is filtered that would help my understanding.
On Thu, Apr 30, 2020 at 10:13 AM Shareef Jalloq
wrote:
> Having no luck here. I've had a read on the LVM config usage and there
> were no filters enabled
Having no luck here. I've had a read on the LVM config usage and there
were no filters enabled in lvm.conf. I enabled debug logging and can see
the default global filter being applied. I then manually forced the 'all'
fiter and 'pvcreate /dev/sdb' still tells me it is excluded by a filter.
The
Actually, now I've fixed that, indeed, the deployment now fails with an lvm
filter error. I'm not familiar with filters but there aren't any
uncommented instances of 'filter' in /etc/lvm/lvm.conf.
On Wed, Apr 29, 2020 at 5:42 PM Shareef Jalloq wrote:
> Ah of course. I was assuming something
Ah of course. I was assuming something had gone wrong with the deployment
and it couldn't clean up its own mess. I'll raise a bug on the
documentation.
Strahil, what are the other options to using /dev/sdxxx?
On Wed, Apr 29, 2020 at 10:17 AM Strahil Nikolov
wrote:
> On April 29, 2020 2:39:05
On April 29, 2020 2:39:05 AM GMT+03:00, Jayme wrote:
>Has the drive been used before, it might have existing
>partition/filesystem
>on it? If you are sure it's fine to overwrite try running wipefs -a
>/dev/sdb on all hosts. Also make sure there aren't any filters setup in
>lvm.conf (there
Has the drive been used before, it might have existing partition/filesystem
on it? If you are sure it's fine to overwrite try running wipefs -a
/dev/sdb on all hosts. Also make sure there aren't any filters setup in
lvm.conf (there shouldn't be on fresh install, but worth checking).
On Tue, Apr
11 matches
Mail list logo
