Bug 1482852
| Summary: | crm_report no longer collects anything for sosreport [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, cluster-maint, djansa, jruemker, kgaillot, michele, mjuricek, rscarazz, tbarron |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 7.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.16-12.el7_4.2 | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, the crm_report utility terminated with a fatal error if the user disabled searching for logs using the --sos-mode option without specifying any log files. Consequently, the sosreport tool was unable to collect any cluster log file. With this update, crm_report now correctly collects non-log information if no logs are found or specified, and the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | 1482278 | Environment: | |
| Last Closed: | 2017-09-05 11:31:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1482278 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-08-18 08:36:23 UTC
Steps to Reproduce: 1. Configure a cluster and run it for a few minutes. 2. Run 'crm_report --sos-mode --from HH:MM:SS --to HH:MM:SS' replacing HH:MM:SS with the desired start and end times. Actual results: Resulting tar file has nothing of interest in it. Expected results: Resulting tar file contains configuration information, policy engine input files, etc. 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-2017:2587 |