Description of problem: A volume created as a "distributed stripe" volume gets recognized by rhsc as a "stripe" volume. volume type recognition is also an issue for "distributed-replicate" volumes Version-Release number of selected component (if applicable): rhsc-bb10 u6 and rhs 2.1 nodes. How reproducible: 50% of the time Steps to Reproduce: 1. in the gui create 2 host cluster 2. create a 2x4 distributed stripe volume with the stripe count set to 4 Actual results: In the volume, main tab, the table displays "stripe" as the volume type for the volume. Selecting the volume opens the general sub-tab for the volume. The general sub-tab shows "stripe" as the volume type. Expected results: main tab and general sub-tab for volume should show "distributed stripe" for the volume type. Additional info:
gluster cli shows that the volume was correctly created by rhsc: [root@dhcp159-176 ~]# gluster volume info Volume Name: automation-volume-distributed-stripe Type: Distributed-Stripe Volume ID: d0aa2b7b-da35-4d45-a5a1-583efd6fa700 Status: Created Number of Bricks: 2 x 4 = 8 Transport-type: tcp Bricks: Brick1: latest-anshi-a:/rhs/brick1/gluster/bricks/distributedStripe/brick1 Brick2: latest-anshi-a:/rhs/brick1/gluster/bricks/distributedStripe/brick2 Brick3: latest-anshi-a:/rhs/brick1/gluster/bricks/distributedStripe/brick3 Brick4: latest-anshi-a:/rhs/brick1/gluster/bricks/distributedStripe/brick4 Brick5: latest-anshi-b:/rhs/brick1/gluster/bricks/distributedStripe/brick1 Brick6: latest-anshi-b:/rhs/brick1/gluster/bricks/distributedStripe/brick2 Brick7: latest-anshi-b:/rhs/brick1/gluster/bricks/distributedStripe/brick3 Brick8: latest-anshi-b:/rhs/brick1/gluster/bricks/distributedStripe/brick4 Options Reconfigured: auth.allow: 10.70.35.63,10.70.35.123 user.cifs: disable nfs.disable: off [root@dhcp159-176 ~]
Created attachment 798415 [details] vdsm log
Created attachment 798416 [details] engine log
verified in rhsc-cb10
Please review the edited DocText and signoff.
doc_text looks good.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html