If the volume create fails due to some reason, there is no logging of the error message and neither do I see any meaniful error on the console to figure out what really wnt wrong. See below: [root@dhcp42-41 ~]# heketi-cli volume create --size=10 --persistent-volume-file=pv001.json Error: docker logs on teh cotainer too have nothing useful to debug: [negroni] Completed 200 OK in 208.298µs [negroni] Started GET /clusters/0f8e46ce836ef0cc66da14fc5aa92ac4 [negroni] Completed 200 OK in 413.617µs [negroni] Started GET /volumes/a7d8b934a572163c1995aa003c736a60 [negroni] Completed 200 OK in 1.804691ms [negroni] Started GET /nodes/3aaac28bba4c47fa18da478fc75b1eea [negroni] Completed 200 OK in 588.055µs [negroni] Started GET /nodes/5202eb162964a814f02395669abf59c0 [negroni] Completed 200 OK in 483.038µs [negroni] Started GET /nodes/ed72981275e1fd8664b4f3b20db75ec2 [negroni] Completed 200 OK in 460.901µs [negroni] Started GET /clusters [negroni] Completed 200 OK in 163.369µs [negroni] Started GET /clusters/0f8e46ce836ef0cc66da14fc5aa92ac4 [negroni] Completed 200 OK in 280.523µs [negroni] Started GET /volumes/a7d8b934a572163c1995aa003c736a60 [negroni] Completed 200 OK in 947.963µs [negroni] Started GET /nodes/3aaac28bba4c47fa18da478fc75b1eea [negroni] Completed 200 OK in 711.588µs [negroni] Started GET /nodes/5202eb162964a814f02395669abf59c0 [negroni] Completed 200 OK in 636.589µs [negroni] Started GET /nodes/ed72981275e1fd8664b4f3b20db75ec2 [negroni] Completed 200 OK in 662.538µs
The errors are definitely logged, I am not sure why they are not showing up. The error "Error: " is definitely bad, and is probably due to the same issue as BZ1350636 *** This bug has been marked as a duplicate of bug 1350636 ***
This is the original bug, mark 1350636 as duplicate of this bug.
*** Bug 1350636 has been marked as a duplicate of this bug. ***
Is this still an issue? Could you please reproduce?
according to the upstream issues this has meanwhile been fixed: https://github.com/heketi/heketi/issues/394 https://github.com/heketi/heketi/issues/412
I've tested this against the latest heketi build (heketi-3.1.0-3.el7rhgs.x86_64) and noticed that heketi server still doesn't log proper error message on any volume create failures. See below: ###### {"log":"[negroni] Started POST /volumes\n","stream":"stdout","time":"2016-11-24T11:04:11.642199782Z"} {"log":"[negroni] Completed 400 Bad Request in 215.879µs\n","stream":"stdout","time":"2016-11-24T11:04:11.642272341Z"} ####### Hence, moving it back to Assigned. PS: heketi-cli seems to correctly print the proper error message to stdout now. But the same should be logged in the server logs as well.
Patch Upstream under review: https://github.com/heketi/heketi/pull/610
(In reply to Mohamed Ashiq from comment #14) > Patch Upstream under review: > > https://github.com/heketi/heketi/pull/610 merged upstream.
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=528156
Verified as fixed in the latest heketi build
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://rhn.redhat.com/errata/RHEA-2017-0148.html