Bug 1468053
| Summary: | [RFE] sosreport should ingest openstack-tripleo-ui logs | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Honza Pokorny <hpokorny> | |
| Component: | sos | Assignee: | Honza Pokorny <hpokorny> | |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Heger <jheger> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.4 | CC: | agk, apannu, beth.white, bmr, gavin, hpokorny, jheger, jreznik, jschluet, mhradile, plambri, pmoravec, salmy, sbradley, toneata | |
| Target Milestone: | rc | Keywords: | FutureFeature, OtherQA, Reopened, ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | sos-3.5-1.el7 | Doc Type: | If docs needed, set a value | |
| Doc Text: |
Previously, the sosreport tool did not collect certain Openstack TripleO logs. Consequently, debugging of TripleO bugs was limited, and the logs had to be requested additionally. This update fixes the sosreport to collect the logs once again. As a result, sosreport now works as expected, and TripleO logs are now
properly collected.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1470573 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 18:01:47 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1467715, 1470573 | |||
|
Description
Honza Pokorny
2017-07-05 23:16:39 UTC
too late for 7.4, acking for 7.5 Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. oops, I wanted devel_ack+, not -, sorry for that! Pavel, we were hoping to release this as 0day errata for 7.4 --- is that possible? (In reply to Honza Pokorny from comment #8) > Pavel, we were hoping to release this as 0day errata for 7.4 --- is that > possible? From devel perspective, I am OK to add it to 7.4 via 0day. Please follow / initiate the process (esp. provide business justification that I miss / dont know at all - I guess the acceptance criteria are met due to layered products point/option) and I am happy to do my part. Not sure if our QE would be able to verify it in the tight timeframe - Miroslav, could you comment? OtherQE would be better in this case. (In reply to Miroslav Hradílek from comment #13) > OtherQE would be better in this case. Honza, could you please confirm you will do OtherQE once I prepare a package? (add OtherQA to keywords for that) Yes, I can handle OtherQE. Re-raising needinfo on Steve: Steve, can you please pm_ack the 0day request? do we have a fixed in version for this bug? (In reply to Jon Schlueter from comment #25) > do we have a fixed in version for this bug? Yes. Cloned [1] was fixed via z-stream errata [2]. This BZ will be fixed in RHEL7.5. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1470573 [2] https://access.redhat.com/errata/RHBA-2017:2331 Fixed via sos 3.5 rebase. I successfully verified the 3.5-2.el7 package on RHEL 7.4. This should be treated as SanityOnly. 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/RHEA-2018:0963 |