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.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Is this still an issue? How was this done? CLI? UI? Can you elaborate more on what causes this issue?
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.
https://review.openstack.org/#/c/376060/
Blueprint is here : https://blueprints.launchpad.net/tripleo-ui/+spec/websocket-logging