Bug 1671559

Summary:	During Hyperconverged deployment with JBOD, error missing diskcount section
Product:	[oVirt] cockpit-ovirt	Reporter:	Jason H. <cakersq>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.12.1	CC:	bugs, gshereme, lleistne, simon.coter, surs
Target Milestone:	ovirt-4.3.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-13 16:40:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jason H. 2019-01-31 22:12:49 UTC

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.

Comment 1 Jason H. 2019-01-31 22:22:56 UTC

Submitted Bug 1671559 (https://bugzilla.redhat.com/show_bug.cgi?id=1671559) to address not being able to edit gdeploy config file.

Comment 2 Jason H. 2019-01-31 22:26:20 UTC

Correction, Submitted Bug 1671561 to address not being able to edit gdeploy config file.

Comment 3 Gobinda Das 2019-02-01 06:30:32 UTC

@sac: Can you please confirm which version of gdeploy this issue solved?

Comment 4 Sachidananda Urs 2019-02-01 06:37:07 UTC

(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.

Comment 5 Jason H. 2019-02-05 11:17:51 UTC

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.

Comment 6 Sachidananda Urs 2019-02-05 11:29:17 UTC

(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.

Comment 7 Simon Coter 2019-02-11 21:44:19 UTC

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

Comment 8 SATHEESARAN 2019-03-12 17:22:16 UTC

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

Comment 9 Sandro Bonazzola 2019-03-13 16:40:29 UTC

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.