Bug 1726461
| Summary: | sosreport doesnt collect symlink dirs in container | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Parikshit Khedekar <pkhedeka> | |
| Component: | sos | Assignee: | Pavel Moravec <pmoravec> | |
| Status: | CLOSED ERRATA | QA Contact: | Miroslav Hradílek <mhradile> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.6 | CC: | agk, bmr, jhunsaker, mhradile, plambri, sbradley | |
| Target Milestone: | rc | Keywords: | OtherQA | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | sos-3.8-1.el7 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1728214 (view as bug list) | Environment: | ||
| Last Closed: | 2020-03-31 20:04:09 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: | 1728214 | |||
|
Comment 2
Pavel Moravec
2019-07-03 06:22:34 UTC
(well now I realized the plugin default timeout is just 300s, so I am curious why the plugin kicked off commands after that limit, but still the problem remains the same: too much activity required from a plugin within given timeout) Re-phrased the subject. This BZ will therefore backport https://github.com/sosreport/sos/pull/1705 . Please provide a reproducer, it works well for me on some default test I run. Or grant OtherQE. Sorry, didn't notice the request for reproducer. As far as I can tell, any recent branch of Atomic Host will show this behavior when sos is run inside the support-tools container. If you sideload the sos rpm into the branch (something no one should be doing), you don't get the errors. It's specifically about running in a container. With #1705, I don't see the exceptions inside a container. (In reply to Jake Hunsaker from comment #7) > Sorry, didn't notice the request for reproducer. > > As far as I can tell, any recent branch of Atomic Host will show this > behavior when sos is run inside the support-tools container. If you sideload > the sos rpm into the branch (something no one should be doing), you don't > get the errors. It's specifically about running in a container. > > With #1705, I don't see the exceptions inside a container. I guess you can then do OtherQE (otherwise our QE does not know what/how to test, I think), please? (evaluating possible candidate to 7.8) Jake, could you pls. verify also this? A yum repository for the build of sos-3.8-1.el7 (task 23200819) is available at: http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/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.8/1.el7/sos-3.8-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.8/1.el7/noarch/ The full list of available rpms is: http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/1.el7/noarch/sos-3.8-1.el7.src.rpm http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.8/1.el7/noarch/sos-3.8-1.el7.noarch.rpm Build output will be available for the next 21 days. sos-03.8 works as expected for me on AH inside the support-tools container now. 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-2020:1127 |