Bug 1485211 - auto block-hosting volume creation is disabled
Summary: auto block-hosting volume creation is disabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: CNS-deployment
Version: cns-3.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: CNS 3.6
Assignee: Jose A. Rivera
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks: 1445448
TreeView+ depends on / blocked
 
Reported: 2017-08-25 06:09 UTC by krishnaram Karthick
Modified: 2018-12-14 11:32 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-11 07:09:46 UTC
Embargoed:


Attachments (Terms of Use)
cns-deploy log and heketi.json files (2.21 KB, application/x-xz)
2017-08-25 10:41 UTC, krishnaram Karthick
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2879 0 normal SHIPPED_LIVE heketi bug fix and enhancement update 2017-10-11 11:07:06 UTC

Description krishnaram Karthick 2017-08-25 06:09:37 UTC
Description of problem:
For the first block-volume creation, heketi should automatically create an underlying block hosting volume and then create a block volume. This is not happening.

Heketi 5.0.0
[heketi] INFO 2017/08/25 01:05:43 Loaded kubernetes executor
[heketi] INFO 2017/08/25 01:05:43 Loaded simple allocator
[heketi] INFO 2017/08/25 01:05:43 GlusterFS Application Loaded
Listening on port 8080
[negroni] Started GET /volumes
[negroni] Completed 200 OK in 1.955343ms
[negroni] Started GET /volumes/7dfe80c375b501c241deceb87e709a30
[negroni] Completed 200 OK in 1.38943ms
[negroni] Started POST /blockvolumes
[negroni] Completed 202 Accepted in 289.786µs
[asynchttp] INFO 2017/08/25 03:29:23 asynchttp.go:125: Started job 0ca206bbce0fbf1064bbd1056adf0487
[heketi] INFO 2017/08/25 03:29:23 Creating block volume 4dbcfa82514896a18923c39b2a2765e6
[negroni] Started GET /queue/0ca206bbce0fbf1064bbd1056adf0487
[negroni] Completed 200 OK in 60.409µs
[heketi] INFO 2017/08/25 03:29:23 No block hosting volumes found in the cluster list
[heketi] ERROR 2017/08/25 03:29:23 /src/github.com/heketi/heketi/apps/glusterfs/app_block_volume.go:83: Failed to create block volume: Block Hosting Volume Creation is Disabled. Create a Block hosting volume and try again.
[asynchttp] INFO 2017/08/25 03:29:23 asynchttp.go:129: Completed job 0ca206bbce0fbf1064bbd1056adf0487 in 39.687343ms
[negroni] Started GET /queue/0ca206bbce0fbf1064bbd1056adf0487
[negroni] Completed 500 Internal Server Error in 76.42µs
[negroni] Started POST /blockvolumes
[negroni] Completed 202 Accepted in 2.615586ms
[asynchttp] INFO 2017/08/25 03:29:36 asynchttp.go:125: Started job 4ebb11f4dac218b5c9cbe9866c5a6ad4
[heketi] INFO 2017/08/25 03:29:36 Creating block volume 5963189b4570a88a52ff368485ea31aa
[heketi] INFO 2017/08/25 03:29:36 No block hosting volumes found in the cluster list
[negroni] Started GET /queue/4ebb11f4dac218b5c9cbe9866c5a6ad4
[negroni] Completed 200 OK in 45.097µs
[heketi] ERROR 2017/08/25 03:29:36 /src/github.com/heketi/heketi/apps/glusterfs/app_block_volume.go:83: Failed to create block volume: Block Hosting Volume Creation is Disabled. Create a Block hosting volume and try again.

This was not the case in the previous builds. This is a regression.

Version-Release number of selected component (if applicable):
cns-deploy-5.0.0-23.el7rhgs.x86_64

How reproducible:
always

Steps to Reproduce:
1. setup CNS
2. create a block-volume without creating block hosting volume
3.

Actual results:
block volume creation fails

Expected results:
block hosting volume should be created and then block volume should be created

Additional info:

Comment 4 Michael Adam 2017-08-25 08:03:19 UTC
btw: why a new bug?
This looks like a failed-qa on
https://bugzilla.redhat.com/show_bug.cgi?id=1468109

Comment 6 krishnaram Karthick 2017-08-25 10:41:45 UTC
Created attachment 1318107 [details]
cns-deploy log and heketi.json files

Comment 7 krishnaram Karthick 2017-08-25 10:43:18 UTC
(In reply to Michael Adam from comment #4)
> btw: why a new bug?
> This looks like a failed-qa on
> https://bugzilla.redhat.com/show_bug.cgi?id=1468109

We don't re-open a bug which is fixed and verified, but open a new bug and raise a regression flag to get it fixed.

Comment 8 Michael Adam 2017-08-25 10:49:33 UTC
(In reply to krishnaram Karthick from comment #7)
> (In reply to Michael Adam from comment #4)
> > btw: why a new bug?
> > This looks like a failed-qa on
> > https://bugzilla.redhat.com/show_bug.cgi?id=1468109
> 
> We don't re-open a bug which is fixed and verified, but open a new bug and
> raise a regression flag to get it fixed.

Ok, thanks for the explanation!

Comment 9 Michael Adam 2017-08-25 11:08:53 UTC
karthick, please provide /etc/heketi/heketi.json

Comment 22 errata-xmlrpc 2017-10-11 07:09:46 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


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