Bug 1297336 - [RFE][UX] collect all errors to the undercloud when a deployment fails
Summary: [RFE][UX] collect all errors to the undercloud when a deployment fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jason E. Rist
QA Contact: Ola Pavlenko
URL:
Whiteboard: NeedsAllocation
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-11 09:30 UTC by Udi Kalifon
Modified: 2018-03-13 15:56 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-13 15:56:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Udi Kalifon 2016-01-11 09:30:23 UTC
Description of problem:
When a deployment fails the user has to dig through a myriad of logs on all nodes and heat resources. Please collect all relevant errors to the failure in an error log on the undercloud - and give a clear message to the user to look in that log.


How reproducible:
100%


Steps to Reproduce:
1. Deploy and fail for some reason


Actual results:
Failure reason is up to the user to determine


Expected results:
Failure reason should be propagated up and be available easily and clearly to the user, on the undercloud.

Comment 3 Mike Burns 2016-04-07 21:03:37 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 5 Jason E. Rist 2016-09-29 11:20:38 UTC
Is this still an issue? How was this done? CLI? UI? Can you elaborate more on what causes this issue?

Comment 6 Udi Kalifon 2016-09-29 11:25:10 UTC
This is still an issue. It's hard for users to see the relevant logs when a failure occurs. There currently is no feature that aggregates all the needed logs in a readable way. This applies equally to the UI as well as CLI.

Comment 7 Ola Pavlenko 2016-10-05 15:06:04 UTC
https://review.openstack.org/#/c/376060/

Comment 8 Ola Pavlenko 2016-10-05 16:58:27 UTC
Blueprint is here :
https://blueprints.launchpad.net/tripleo-ui/+spec/websocket-logging


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