Description of problem: User Story Epic As a Cloud Ops administrator I want to view all deployment service logs form a log common to all OpenStack components, that are relevant to the deployment in an easy to understand manner so that I can review the components, actions and data used in the deployment for monitoring and diagnosis. Tests: 1.Review the set up of the RabbitMQ cluster from the logs post-deployment - all information about RabbitMQ that is recorded during a RabbitMQ deployment should be present Constraints: Might need to interact with Common Logging Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Waiting on one patch: https://review.openstack.org/#/c/469608- almost merged, finally passing CI
All external trackers for patches have been merged and are in OSP 12
The related ticket has just been moved to MODIFIED. Once it passes QA, we can close this as well. https://bugzilla.redhat.com/show_bug.cgi?id=1513453
referenced external trackers included in builds
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
All we have is the ability to download the logs. The bug also requires being able to easily find logs related to specific services, and logs with deployment errors (overcloud), which remains unimplemented. Please advise us on how to test this bug.
assigning the needinfo
The logging in question only relates to the web application. Viewing or manipulating other logs is outside the scope of this ticket. You can use sosreport to get those logs if you need them.
the fix only deals with the UI logs and not any other service. open a new bug if you want to handle what we have in the sosreports via the GUI also.
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/RHBA-2018:2574