[openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon
sombrafam at gmail.com
Mon Apr 13 14:00:15 UTC 2015
I like Duncan's idea. To have a dash in horizon where admin can see error
events. It can hide backend details from tenants and would save the time
of browsing through logs seeking for the operations that caused errors
(the request id also should be logged in the metadata to allow further
investigation). We have notice this problem while ago, and at the time we
found this bug about the same problem.
On Fri, Apr 10, 2015 at 5:26 PM, gordon chung <gord at live.ca> wrote:
> > I'd say events are *more* useful in that workflow, not less, as long as
> > they contain enough context. For example, the user creates a volume,
> > tries to attach it which fails for some config error, so the user
> > deletes it. With an event based model, the admin now has an error event
> > in their queue. If we used a db field then the error status is
> > potentially revived by the successful delete.
> Nova currently emits a good set of events and errors and we've found it
> especially useful to debug / do postmortem analysis by collecting these
> notifications and being able to view the entire workflow. we've found quite
> a few occasions where the error popups presented in Horizon are not the
> real error but just the last/wrapped error.
> there are various consumers that already collate these error notifications
> from Nova and i don't think it's much of a change if any to collect error
> notifications from Cinder. i don't think there's any change from Ceilometer
> POV -- just publish to error topic.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev