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
I will be closing this bug and will add the comments to rhhi bug.