Bug 1677827 - no option for "disc count" for JBOD
Summary: no option for "disc count" for JBOD
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Gdeploy
Version: 0.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-16 05:04 UTC by Jason Brooks
Modified: 2019-02-27 10:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-27 10:33:03 UTC
oVirt Team: Gluster
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.