Description of problem: ------------------------ Order of the hosts is not preserved and it won't be the problem for replicated volume, but for the arbitrated volume, gluster-ansible role would place the arbiter brick on any of the host against the users expectation. Version-Release number of selected component (if applicable): ------------------------------------------------------------- gluster-ansible-roles-1.0.4-4 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Create the vars file with hostnames in order host1, host2, host3 2. Create volumes Actual results: --------------- volumes are created with different order of bricks - say host2, host3, host1 Expected results: ----------------- Volume should be created in the same order as listed in the vars file Additional info:
When I tested I see the bricks are created in the order provided: Vars: gluster_features_hci_volumes: - { volname: 'data', brick: '/data-1/data' } - { volname: 'engine', brick: '/data-1/engine' } - { volname: 'store', brick: '/data-1/store' } gluster_features_hci_cluster: - host2 - host3 - host1 Result: Volume Name: store Type: Replicate Volume ID: 7b03f1d3-8dac-4235-a6a6-fb2e650a6f57 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: host2:/data-1/store Brick2: host3:/data-1/store Brick3: host1:/data-1/store Options Reconfigured: Volume Name: engine Type: Replicate Volume ID: acc4b7a9-2eec-4116-819b-ae8f51d19ed3 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: host2:/data-1/engine Brick2: host3:/data-1/engine Brick3: host1:/data-1/engine Options Reconfigured: Volume Name: data Type: Replicate Volume ID: aeeb2cd5-6c53-4365-baaa-016ab07059d8 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: host2:/data-1/data Brick2: host3:/data-1/data Brick3: host1:/data-1/data Options Reconfigured: cluster.granular-entry-heal: enable ====================================================== There is no sorting happening.
The same bug was raised in earlier version and please see my comment below: https://bugzilla.redhat.com/show_bug.cgi?id=1636427#c3 If this is still happening, could be a regression in cockpit plugin. Please attach the generated variable file as well. The reason for this is using groups['hosts'] and we should not be using that till Ansible fixes the bug: https://github.com/ansible/ansible/issues/34861
(In reply to Sachidananda Urs from comment #1) > When I tested I see the bricks are created in the order provided: > > Vars: > gluster_features_hci_volumes: > - { volname: 'data', brick: '/data-1/data' } > - { volname: 'engine', brick: '/data-1/engine' } > - { volname: 'store', brick: '/data-1/store' } > gluster_features_hci_cluster: > - host2 > - host3 > - host1 Sac, vars file is generated as: <snip> cluster_nodes: - host10.lab.eng.blr.redhat.com - host11.lab.eng.blr.redhat.com - host12.lab.eng.blr.redhat.com gluster_features_hci_cluster: '{{ cluster_nodes }}' gluster_features_hci_volumes: - volname: engine brick: /gluster_bricks/engine/engine arbiter: 0 - volname: data brick: /gluster_bricks/data/data arbiter: 1 - volname: vmstore brick: /gluster_bricks/vmstore/vmstore arbiter: 0 - volname: extravol1 brick: /gluster_bricks/extravol1/extravol1 arbiter: false </snip> In this case the order of the host is not preserved. Sac, Could you help finding the actual problem ?
@Gobinda, The workaround for now is to remove the volume altogether and create it fresh from RHV Manager UI. I don't think there exists a mechanism to remove the arbiter brick from some node and add to someother node
Thanks sas
The dependent bug is ON_QA and also moving this bug ON_QA
Tested with cockpit-ovirt-dashboard 0.12.8 The bricks are created on the hosts in the given order. Volume Name: engine Type: Replicate Volume ID: 8b81d419-6994-48d3-993b-95a99e9a07f2 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: host1:/gluster_bricks/engine/engine Brick2: host2:/gluster_bricks/engine/engine Brick3: host3:/gluster_bricks/engine/engine
As this bug is fixed, the known_issue related to this bug becomes void. Also no doc_text required for this bug fix, as this problem popped-up in the interim builds and not from previous version of release