On upgrading heketi, creation of file and block volumes got disabled on existing clusters. With this fix, heketi does not disable file and block volume creation.
Descriptionkrishnaram Karthick
2017-10-03 08:06:15 UTC
Description of problem:
After upgrading from cns 3.5 to 3.6 following the steps outlined in [1], new volume creation fails.
heketi-cli volume create --size=1
Error: No space
[heketi] INFO 2017/10/03 08:01:14 Creating volume 3c70fa03cac988ec7c55bd8cf632679a
[heketi] ERROR 2017/10/03 08:01:14 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:290: Volume being ask to be created, but there are no clusters configured
[negroni] Started GET /queue/2cc3e5a3f570f92bf1e9aed73f531ccd
[negroni] Completed 200 OK in 47.91µs
[asynchttp] INFO 2017/10/03 08:01:14 asynchttp.go:129: Completed job 2cc3e5a3f570f92bf1e9aed73f531ccd in 115.386862ms
[heketi] ERROR 2017/10/03 08:01:14 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:149: Failed to create volume: No space
[negroni] Started GET /queue/2cc3e5a3f570f92bf1e9aed73f531ccd
[negroni] Completed 500 Internal Server Error in 89.654µs
heketi-cli cluster list
Clusters:
Id:83767272f27df11472bb41f0318ba7a5 []
file and block access for the cluster seems to be missing from the above output.
[1] - https://access.qa.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/container-native_storage_for_openshift_container_platform/#idm140661927080880
Version-Release number of selected component (if applicable):
cns-deploy-5.0.0-52.el7rhgs.x86_64
How reproducible:
1/1
Steps to Reproduce:
1. upgrade cns 3.5 to 3.6
2. provision volumes after the upgrade
Comment 4krishnaram Karthick
2017-10-03 08:10:15 UTC
Comment 11Raghavendra Talur
2017-10-05 09:27:11 UTC
doc text looks good to me
Comment 12krishnaram Karthick
2017-10-09 06:47:00 UTC
Verified the bug in build - cns-deploy-5.0.0-54.el7rhgs.x86_64
Fresh volume creation works and block volume creation is successful after the upgrade.
Moving the bug to verified.
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