Description of problem: When deployed Hosted Engine using Cockpit Dashboard, selecting JBOD results in error missing diskcount section Version-Release number of selected component (if applicable): 0.12.1 How reproducible: Always Steps to Reproduce: 1. Open Cockpit > Virtualization > Hosted Engine 2. Click on Hyperconverged > Run Gluster Wizard 3. Under Bricks step, RAID Information, select JBOD Actual results: Error: Section diskcount not found in the configuration file Expected results: Gluster deployment Additional info: Manually editing Deployment file, and adding "[diskcount]" section with "1" underneath does not fix issue.
Submitted Bug 1671559 (https://bugzilla.redhat.com/show_bug.cgi?id=1671559) to address not being able to edit gdeploy config file.
Correction, Submitted Bug 1671561 to address not being able to edit gdeploy config file.
@sac: Can you please confirm which version of gdeploy this issue solved?
(In reply to Gobinda Das from comment #3) > @sac: Can you please confirm which version of gdeploy this issue solved? This is fixed in gdeploy-2.0.11 in upstream. However, CentOS is yet to release it since CentOS does not have Ansible > 2.5 yet.
Thanks. Note that my hosts have Ansible version 2.7.6 (ansible-2.7.6-1.el7.noarch), included by the ovirt-4.3-dependencies.repo.
(In reply to Jason H. from comment #5) > Thanks. Note that my hosts have Ansible version 2.7.6 > (ansible-2.7.6-1.el7.noarch), included by the ovirt-4.3-dependencies.repo. Thanks for that information Jason, I'll try to convince CentOS maintainers to release the package based on this.
FYI, just for confirmation, I got the same issue and the same has been fixed by gdeploy-2.0.11 I've got from: https://cbs.centos.org/koji/buildinfo?buildID=25063 Ansible release in-place is: ansible-2.7.6-1.el7.noarch
Tested with cockpit-ovirt-dashboard-0.12.4 JBOD disktype, doesn't need the disk count. Performance parameters for the JBOD drives are already taken in to consideration while creating the PVs, VGs, thinpool, thinLVs
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 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.