Created attachment 1545963 [details] RAID INFIRMATION SCREENSHOT +++ This bug was initially created as a clone of Bug #1690797 +++ Description of problem: ------------------------ If the user switches from RAID type JBOD to RAID 5,RAID6 the stripe size and disk count parameter are empty. Where as the stripe size and data disk count should be reflected automatically when the RAID type is changed. Version-Release number of selected component: ---------------------------------------------- glusterfs-server-3.12.2-47.el7rhgs gluster-ansible-repositories-1.0-1.el7rhgs.noarch gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch gluster-ansible-features-1.0.4-5.el7rhgs.noarch gluster-ansible-cluster-1.0-1.el7rhgs.noarch gluster-ansible-roles-1.0.4-4.el7rhgs.noarch gluster-ansible-infra-1.0.3-3.el7rhgs.noarch rhvh-4.3.0.5-0.20190313 How reproducible: ------------------ Everytime Steps to Reproduce: -------------------- 1.Login to the cockpit UI and click on hyperconverged. 2.Fill in the parameters in host,FQDN and volume tabs. 3.Issue can be seen in brick tab. Actual results: ---------------- The data disk count and stripe size is not reflected when once the RAID type is changed from JBOD to RAID 5 or RAID 6. Expected results: ----------------- The data disk count and stripe size should be reflected .
The data diskcount and stripe size default values are present when the disktype is changed from "JBOD" to " RAID5 " and " RAID6". Hence , moving the bug to verified state.
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.