Bug 1341961 - heketi server doesn't log errors for node/device delete
Summary: heketi server doesn't log errors for node/device delete
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: CNS 3.4
Assignee: Mohamed Ashiq
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1385246
TreeView+ depends on / blocked
 
Reported: 2016-06-02 07:22 UTC by Neha
Modified: 2017-01-18 21:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-18 21:55:07 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1341141 0 medium CLOSED heketi-cli: proper error message to stdout for cluster/node/device delete 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2017:0148 0 normal SHIPPED_LIVE heketi bug fix and enhancement update 2017-01-19 02:53:24 UTC

Internal Links: 1341141

Description Neha 2016-06-02 07:22:03 UTC
Description of problem:

for node delete:

Logs:
[negroni] Started DELETE /nodes/53bb0c58ceaa2042c5088377de9c872f
[negroni] Completed 409 Conflict in 323.013µs

for device delete

Logs:
[negroni] Started DELETE /devices/77fddc8c8ed815ab09965095941cf899
[negroni] Completed 409 Conflict in 368.05µs

for example cluster delete , it log proper error message.

Logs:
[negroni] Started DELETE /clusters/46d613cf778d1a11ab2f36a2dd3dc803
[heketi] WARNING 2016/05/27 12:01:01 Unable to delete cluster [46d613cf778d1a11ab2f36a2dd3dc803] because it contains volumes and/or nodes
[negroni] Completed 409 Conflict in 466.033µs

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
=> Try to delete a node which contains devices
=> Try to delete a device which contains volumes/bricks

Actual results:
server doesn't return proper error message.

Expected results:
Should log proper error message

Additional info:
https://github.com/heketi/heketi/issues/367

Comment 9 Prasanth 2016-11-24 10:33:32 UTC
I've tested this against the latest heketi build (heketi-3.1.0-3.el7rhgs.x86_64) and noticed that heketi server logs still doesn't log proper error message on deletion of nodes and devices. See below:

######
[negroni] Started DELETE /nodes/494b9461066aef3c45412789a678f64c
[negroni] Completed 409 Conflict in 478.777µs
[negroni] Started GET /nodes/494b9461066aef3c45412789a678f64c
[negroni] Completed 200 OK in 1.54354ms
[negroni] Started DELETE /devices/99a185888a45bf9fdc804433d1cd840b
[negroni] Completed 409 Conflict in 489.798µs
#######

Hence, moving it back to Assigned.

Comment 11 Mohamed Ashiq 2016-12-06 07:10:46 UTC
Patch Upstream under review:

https://github.com/heketi/heketi/pull/607

Comment 12 Mohamed Ashiq 2016-12-07 11:43:57 UTC
(In reply to Mohamed Ashiq from comment #11)
> Patch Upstream under review:
> 
> https://github.com/heketi/heketi/pull/607

merged upstream.

Comment 14 Prasanth 2016-12-27 07:04:18 UTC
###############
[negroni] Started DELETE /nodes/02aa429ce9115bb462a55e96230bb8da
[negroni] Completed 409 Conflict in 351.923µs
[heketi] ERROR 2016/12/27 06:59:30 /src/github.com/heketi/heketi/apps/glusterfs/app_node.go:231: Unable to delete node [02aa429ce9115bb462a55e96230bb8da] because it contains devices


[negroni] Started DELETE /devices/2c4543d63de3738b623f3210d849ae2f
[heketi] ERROR 2016/12/27 07:00:53 /src/github.com/heketi/heketi/apps/glusterfs/app_device.go:229: Unable to delete device [2c4543d63de3738b623f3210d849ae2f] because it contains bricks
[negroni] Completed 409 Conflict in 1.312799ms
###############

Comment 15 Prasanth 2016-12-27 07:05:15 UTC
Verified as fixed in the latest heketi build

Comment 17 errata-xmlrpc 2017-01-18 21:55:07 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://rhn.redhat.com/errata/RHEA-2017-0148.html


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