Bug 1786457

Summary:	[ceph-dashboard]iSCSI: Edit target of more than one parameter causes exception dashboard.rest_client.RequestException: iscsi REST API failed request with status code 400
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Madhavi Kasturi <mkasturi>
Component:	Ceph-Dashboard	Assignee:	Ernesto Puerta <epuertat>
Status:	CLOSED ERRATA	QA Contact:	Sunil Angadi <sangadi>
Severity:	high	Docs Contact:	Bara Ancincova <bancinco>
Priority:	medium
Version:	4.0	CC:	ceph-eng-bugs, ceph-qe-bugs, epuertat, hyelloji, jdillama, kdreyer, knortema, sangadi, tserlin
Target Milestone:	rc	Keywords:	TestBlocker
Target Release:	4.1	Flags:	hyelloji: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-14.2.8-3.el8, ceph-14.2.8-3.el7	Doc Type:	Known Issue
Doc Text:	.The Dashboard does not provide correct Ceph iSCSI error messages If the Ceph iSCSI returns an error, for example the HTTP "400" code when trying to delete an iSCSI target while a user is logged in, the {product} Dashboard does not forward that error code and message to the Dashboard user using the pop-up notifications, but displays a generic "500 Internal Server Error". Consequently, the message that the Dashboard provides is not informative and even misleading; an expected behavior ("users cannot delete a busy resource") is perceived as an operational failure ("internal server error"). To work around this issue, see the Dashboard logs.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-19 17:31:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1730176, 1816167

Comment 2 Jason Dillaman 2020-01-06 17:17:07 UTC

While it is unfortunate that the UI is not providing a nice error message, this should always fail. Note the error of "Client xyz is logged in to abc - unable to delete until it's logged out". You cannot delete a client that is still logged into the target and therefore you must log out the client first. Therefore, the severity should be reduced and this should not be a test blocker unless you cannot delete a logged out client.

Comment 3 Ernesto Puerta 2020-01-08 12:25:20 UTC

*** Bug 1786258 has been marked as a duplicate of this bug. ***

Comment 22 errata-xmlrpc 2020-05-19 17:31:40 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/RHSA-2020:2231