Description of problem: With blockhosting volume of size 100 GB, blockvolume create of size >100Gb fails with a vague error message. # heketi-cli blockvolume create --size=120 Error: Unable to execute command on glusterfs-storage-pgbjn: # oc rsh heketi-storage-1-xznlb sh-4.2# rpm -qa | grep 'heketi' heketi-client-6.0.0-5.el7rhgs.x86_64 python-heketi-6.0.0-5.el7rhgs.x86_64 heketi-6.0.0-5.el7rhgs.x86_64 sh-4.2# This was not the case in CNS 3.6, # rpm -qa | grep 'heketi' heketi-client-5.0.0-19.el7rhgs.x86_64 # heketi-cli blockvolume create --size=600 Error: Default Block Hosting Volume size is less than block volume requested. # oc rsh heketi-1-dm835 sh-4.2# rpm -qa | grep 'heketi' heketi-client-5.0.0-19.el7rhgs.x86_64 python-heketi-5.0.0-19.el7rhgs.x86_64 heketi-5.0.0-19.el7rhgs.x86_64 sh-4.2# Hence, this is a regression Version-Release number of selected component (if applicable): Heketi 6.0.0 How reproducible: Always Steps to Reproduce: 1. create a blockhosting volume of size 100Gb 2. Try to create a block device of size > 100Gb Actual results: create request fails with error 'Error: Unable to execute command on glusterfs-storage-pgbjn: Expected results: proper error message as seen in CNS 3.6 Additional info: heketi logs shall be attached.
This issue is fixed in build - heketi-6.0.0-7.el7rhgs A proper error message is now presented to the user. [root@dhcp46-101 ~]# heketi-cli blockvolume create --size=400 Error: Failed to allocate new block volume: The size configured for automatic creation of block hosting volumes (100) is too small to host the requested block volume of size 400. Please create a sufficiently large block hosting volume manually.
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-2018:0638
*** Bug 1511302 has been marked as a duplicate of this bug. ***