Bug 1591433
| Summary: | Collect imgbased.log in sosreport | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | nijin ashok <nashok> | |
| Component: | sos | Assignee: | Pavel Moravec <pmoravec> | |
| Status: | CLOSED ERRATA | QA Contact: | Miroslav Hradílek <mhradile> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.5 | CC: | agk, aperotti, bmr, gavin, lsurette, mhradile, nsoffer, plambri, pmoravec, sbradley, srevivo, ycui | |
| Target Milestone: | pre-dev-freeze | Keywords: | OtherQA, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | sos-3.7-1.el7 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1656732 1658937 (view as bug list) | Environment: | ||
| Last Closed: | 2019-08-06 13:15:20 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Sub-Eng | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1656732, 1658937 | |||
|
Description
nijin ashok
2018-06-14 17:43:28 UTC
I think this should be moved to sos project. A specific plugin for imgbased should be created. I agree with Sandro, vdsm should not collect log it does not generate, and new functionality should be only in the sos project. It would be nice if you also file a bug for: - separating sanlock.log to its own sos plugin - adding plugin for ovirt-imageio I think both bugs should be filed for the sos project. I'm also changing the title of the bug. Bug should not specify the solution but the problem. Ack. Moved the bug to sos project. > - separating sanlock.log to its own sos plugin We've had this in mainline sos since 2012. > - adding plugin for ovirt-imageio We added this in August last year. (why I was not automatically assigned to the BZ on changing component to sos? sigh..) devel_ack+ for 7.7, optionally also for 7.6 if other ACKs will be granted (just coincidentally we are doing re-spin around these days..) please grant OtherQE (to let get qa_ack+) and describe business justification (for pm_ack+). (In reply to Pavel Moravec from comment #6) > please grant OtherQE (to let get qa_ack+) and describe business > justification (for pm_ack+). imgbased.log log contains upgrade/installation logs of RHV-H . This log file is necessary for troubleshooting upgrade/installation issues of RHV-H, so in order to have it in next RHVH, is important to have this part of RHEL asap, so 7.6 . thanks (pre-agreed with Andrea he will test the plugin once ready) We didnt catch re-spin on time before blocker+ is required, and the BZ severity/priority does not qualify it to be RHEL7.6 blocker. Hence deferring the BZ to RHEL7.7 and potential/probable inclusion in 7.6.z. GSSApproved for 7.6.2 pushed to 7.7 dist-git in commit 3fe7ccc Hello, could you please verify the BZ against below build? Thanks in advance. A yum repository for the build of sos-3.7-1.el7 (task 20748546) is available at: http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el7/ You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory: http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el7/sos-3.7-1.el7.repo RPMs and build logs can be found in the following locations: http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el7/noarch/ The full list of available rpms is: http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el7/noarch/sos-3.7-1.el7.src.rpm http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el7/noarch/sos-3.7-1.el7.noarch.rpm Build output will be available for the next 21 days. 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-2019:2295 |