Bug 1297336 - [RFE][UX] collect all errors to the undercloud when a deployment fails
[RFE][UX] collect all errors to the undercloud when a deployment fails
Status: NEW
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Jason E. Rist
Ola Pavlenko
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2016-01-11 04:30 EST by Udi
Modified: 2018-01-30 22:03 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Udi 2016-01-11 04:30:23 EST
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:

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 17:03:37 EDT
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 07:20:38 EDT
Is this still an issue? How was this done? CLI? UI? Can you elaborate more on what causes this issue?
Comment 6 Udi 2016-09-29 07:25:10 EDT
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 11:06:04 EDT
Comment 8 Ola Pavlenko 2016-10-05 12:58:27 EDT
Blueprint is here :

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