Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1677827

Summary: no option for "disc count" for JBOD
Product: [oVirt] cockpit-ovirt Reporter: Jason Brooks <jbrooks>
Component: GdeployAssignee: Gobinda Das <godas>
Status: CLOSED NOTABUG QA Contact: SATHEESARAN <sasundar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.12.0CC: bugs
Target Milestone: ---   
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-02-27 10:33:03 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 Brooks 2019-02-16 05:04:06 UTC 
Description of problem:

Installing w/ JBOD leads to the error:

 Error: Section diskcount not found in the configuration file

Version-Release number of selected component (if applicable):

gdeploy-2.0.8-1.el7.noarch

How reproducible:

Install hyperconverged gluster w/ jbod (I tested w/ one disk)

Actual results:

Error: Section diskcount not found in the configuration file

Expected results:

Installation proceeds

Additional info:

I worked around it by adding the missing section to my config file:

[diskcount]
1

Also, the version from the drop down was required, but doesn't correspond to the version of the package, and I didn't know which team to tag.
Comment 1 Gobinda Das 2019-02-18 13:47:33 UTC 
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 2 Jason Brooks 2019-02-18 15:07:45 UTC 
Can we take ansible 2.7 from epel? oVirt does use some deps from there.
Comment 3 Gobinda Das 2019-02-27 10:33:03 UTC 
This bug fixed in ovirt-4.3.1. So closing this.Please reopen if find any issue.