Bug 1468109

Summary: provide a heketi image with auto_create_block_hosting_volume enabled by default
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: krishnaram Karthick <kramdoss>
Component: heketiAssignee: Mohamed Ashiq <mliyazud>
Status: CLOSED ERRATA QA Contact: krishnaram Karthick <kramdoss>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: cns-3.6CC: hchiramm, madam, mliyazud, pprakash, rhs-bugs, storage-qa-internal, vinug
Target Milestone: ---Keywords: TestBlocker
Target Release: CNS 3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: heketi-5.0.0-4 rhgs-volmanager-docker-3.3.0-6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-11 07:07:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1445448    

Description krishnaram Karthick 2017-07-06 05:58:38 UTC
Description of problem:
With the rhgs3/rhgs-volmanager-rhel7:3.3.0-3 image, auto_create_block_hosting_volume is not enabled by default. As a result, block devices can't be created.

Block device create fails

[root@dhcp47-10 ~]# heketi-cli blockvolume create --size 10
Error: Block Hosting Volume Creation is Disabled. Create a Block hosting volume and try again.

Please provide a new heketi image with auto_create_block_hosting_volume enabled by default.


Version-Release number of selected component (if applicable):
heketi image - rhgs3/rhgs-volmanager-rhel7:3.3.0-3

How reproducible:
Always

Steps to Reproduce:
1. Try to create a block device with the above mentioned image

Actual results:
block vol creation fails

Expected results:
block vol creation should succeed

Additional info:

Comment 8 errata-xmlrpc 2017-10-11 07:07:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:2879