Description of problem: Customer is looking for director plug-in or script which collects sosreports from all the controllers and nodes at a single place instead of manually capturing from respective nodes. This would make log collection easier, esp when we require them multiple times if its a random sporadic issue. This request is similar to what we currently have in RHEV as rhev log collector.
In Pike the upstream merged https://blueprints.launchpad.net/tripleo/+spec/capture-environment-status-and-logs which might cover this request.
From comment #2 it evident, that this feature is already available upstream and properly documented [1]. [1] https://docs.openstack.org/tripleo-docs/latest/install/troubleshooting/troubleshooting-log-and-status-capture.html
*** Bug 1246653 has been marked as a duplicate of this bug. ***
Hi Angela, this RFE came late in the cycle to be productized in OSP12. The feature might have landed upstream but for OSP12 we don't have extra QE capacity to test this. We will try to target for OSP13 given it has been already merged. -- Jarda
work is currently ongoing within DF to make sosreport collection simpler, moving to 17 to reflect the investment.
Hey, Does this still need to be open? The requested functionality is there and documented since at least 13: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/command_line_interface_reference/overcloud#overcloud_support_report_collect https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/troubleshooting/troubleshooting-log-and-status-capture.html https://opendev.org/openstack/python-tripleoclient/src/branch/master/tripleoclient/v2/overcloud_support.py Was there something else we wanted to do with the one before closing?
This was added here: https://github.com/openstack/python-tripleoclient/commit/1e69403a9e8dd6084598d6005448c8fcc4835f20 So we'll close this one, since the requested feature is implemented and available.