Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create volume fail, but the volumes are created #28

Open
ita-dips opened this issue Mar 10, 2023 · 0 comments
Open

Create volume fail, but the volumes are created #28

ita-dips opened this issue Mar 10, 2023 · 0 comments

Comments

@ita-dips
Copy link

Create volume fail with msg: "Brick may be containing or be contained by an existing brick"

This is the task:

  • name: "{{ volume.name }} : Creates volume"
    gluster.gluster.gluster_volume:
    state: "{{ volume.state | default('present') }}"
    name: "{{ volume.name }}"
    bricks: "{{ glusterfs_base_path + '/' + volume.name }}/brick1"
    replicas: "{{ volume.replicas | default( glusterfs_nodes | length) }}"
    cluster: "{{ glusterfs_nodes }}"
    force: true
    run_once: true

The error returned is:
TASK [glusterfs : storage1 : Creates volume] *******************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoneType: None
fatal: [dips1-test]: FAILED! => {
"changed": false
}

MSG:

error running gluster (/usr/sbin/gluster --mode=script volume add-brick storage1 replica 3 dips1-test:/var/spool/gluster_brick//storage1/brick1 dips2-test:/var/spool/gluster_brick//storage1/brick1 dips3-test:/var/spool/gluster_brick//storage1/brick1) command (rc=1): volume add-brick: failed: Brick: dips1-test:/var/spool/gluster_brick/storage1/brick1 not available. Brick may be containing or be contained by an existing brick.

But on hosts the volume is created:
~# gluster volume info

Volume Name: storage1
Type: Replicate
Volume ID: d72f03a4-c128-4a01-9986-658eeb52ed2c
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: dips1-test:/var/spool/gluster_brick/storage1/brick1
Brick2: dips2-test:/var/spool/gluster_brick/storage1/brick1
Brick3: dips3-test:/var/spool/gluster_brick/storage1/brick1
Options Reconfigured:
auth.allow: 127.0.0.1,10.44.107.*
performance.quick-read: on
performance.write-behind: off
performance.cache-size: 128MB
cluster.granular-entry-heal: on
storage.fips-mode-rchecksum: on
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off

Versions of tools:
~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

~# glusterd -V
glusterfs 10.1

~# ansible-galaxy collection list
gluster.gluster 1.0.2

~# ansible-playbook --version
ansible-playbook [core 2.14.3]
config file = /var/lib/playbooks/ubuntu/ansible.cfg
configured module search path = ['/var/lib/playbooks/generic/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
ansible collection location = /var/lib/playbooks/ansible_galaxy/collections
executable location = /usr/bin/ansible-playbook
python version = 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] (/usr/bin/python3)
jinja version = 3.0.3
libyaml = True

Any help is appreciate.
Cheers,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant