Bug 1174133
| Summary: | [7.0-3.5]Throw traceback error info when using "sosreport" command to collect diagnostic and configuration information from rhevh | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | haiyang,dong <hadong> |
| Component: | sos | Assignee: | Pavel Moravec <pmoravec> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | agk, cshao, dkutalek, ecohen, fdeutsch, gouyang, hadong, huiwa, iheim, leiwang, lsurette, pmoravec, ycui |
| Target Milestone: | pre-dev-freeze | ||
| Target Release: | 7.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-04 10:51:39 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: | |||
|
Description
haiyang,dong
2014-12-15 08:50:06 UTC
Moving this to sos, as it seems to be a generic traceback if that path is not mounted/existant. > plugin vdsm does not install, skipping: No module named config This is because the vdsm plugin is still not upstream... The monkey patched version is probably broken for sos-3 again. I'm really not clear on what's going on in the copy_dir backtrace and I cannot reproduce it on a vanilla RHEL7 system: # sosreport -v --batch --debug -o system sosreport (version 3.0) This command will collect diagnostic and configuration information from this Red Hat Enterprise Linux system and installed applications. An archive containing the collected information will be generated in /var/tmp and may be provided to a Red Hat support representative. Any information provided to Red Hat will be treated in accordance with the published support policies at: https://access.redhat.com/support/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Running plugins. Please wait ... Running 1/1: system... Creating compressed archive... Your sosreport has been generated and saved in: /var/tmp/sosreport-bmr-rhel7-vm1-20141215143547.tar.xz The checksum is: a27fddeb3dcfdc3ba959683ad39f98c7 Please send this file to your support representative. Running 56/65: system... system Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/sos/sosreport.py", line 974, in collect File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 597, in collect File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 338, in do_copy_file_or_dir File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 294, in copy_dir File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 338, in do_copy_file_or_dir File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 294, in copy_dir File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 338, in do_copy_file_or_dir File "/usr/lib/python2.7/site-packages/sos/plugins/__init__.py", line 293, in copy_dir OSError: [Errno 19] No such device: '/proc/sys/fs/binfmt_misc' Is there something strange about binfmt_mist support on RHEV / RHEL-7 systems? "No such device" is a very surprising error here (esp. inside copy_dir.. which is the correct method to pick up this path). Is there a system where this reproduces that I can log into to run some tests? Even with binfmt_misc unmounted this works fine for me: # umount /proc/sys/fs/binfmt_misc # sosreport -v --batch --debug -o system sosreport (version 3.0) This command will collect diagnostic and configuration information from this Red Hat Enterprise Linux system and installed applications. An archive containing the collected information will be generated in /var/tmp and may be provided to a Red Hat support representative. Any information provided to Red Hat will be treated in accordance with the published support policies at: https://access.redhat.com/support/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Running plugins. Please wait ... Running 1/1: system... Creating compressed archive... Your sosreport has been generated and saved in: /var/tmp/sosreport-bmr-rhel7-vm1-20141215143816.tar.xz The checksum is: 0557215d0a447c13542186748a094313 Please send this file to your support representative. Is there a reproducer machine available, please? That would speedup our investigation a lot.. No such issue on rhev-hypervisor-7.1 (20150420.0.el7ev) for rhev 3.5.1 GA with sos-3.2-15.el7_1.1.noarch. Only occur on rhev-hypervisor 7.0 build, and so far we no longer build/respin rhev-hypervisor 7.0 build future. So this bug can be closed as current release if all agree. Thanks. (In reply to Ying Cui from comment #11) > No such issue on rhev-hypervisor-7.1 (20150420.0.el7ev) for rhev 3.5.1 GA > with sos-3.2-15.el7_1.1.noarch. > > Only occur on rhev-hypervisor 7.0 build, and so far we no longer > build/respin rhev-hypervisor 7.0 build future. > > So this bug can be closed as current release if all agree. Thanks. No objection against closing it from my side. Closing this according to comment 11 and comment 12. |