RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1174133 - [7.0-3.5]Throw traceback error info when using "sosreport" command to collect diagnostic and configuration information from rhevh
Summary: [7.0-3.5]Throw traceback error info when using "sosreport" command to collect...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: pre-dev-freeze
: 7.1
Assignee: Pavel Moravec
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 08:50 UTC by haiyang,dong
Modified: 2019-07-16 11:30 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-04 10:51:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description haiyang,dong 2014-12-15 08:50:06 UTC 
Description of problem:
Although using "sosreport" command to collect diagnostic and configuration information from rhevh
success, but it was thrown traceback error info like follow:
[root@dhcp-9-55 admin]# sosreport 

sosreport (version 3.0)

plugin vdsm does not install, skipping: No module named config
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.

Press ENTER to continue, or CTRL-C to quit.

Please enter your first initial and last name [dhcp-9-55.nay.redhat.com]: 
Please enter the case number that you are generating this report for: 

glusterfs: no process found
glusterfsd: no process found
 Running plugins. Please wait ...

  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'

  Running 65/65: yum...              
Creating compressed archive...

Your sosreport has been generated and saved in:
  /var/tmp/sosreport-dhcp-9-55.nay.redhat.com-20141213103028.tar.xz

The checksum is: 7c98d8120455e3e2a6168b8d39247a93

Please send this file to your support representative.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.0-20141119.0.el7ev
ovirt-node-3.1.0-0.27.20141119git24e087e.el7.noarch


How reproducible:
100%

Steps to Reproduce:
1. Install rhev-hypervisor7-7.0-20141119.0.el7ev
2. Press F2 on TUI to shell and execute "sosreport"

Actual results:
Throw traceback error info when using "sosreport" command to collect diagnostic and configuration information from rhevh

Expected results:
No traceback error info was thrown when using "sosreport" command to collect diagnostic and configuration information from rhevh.

Additional info:

--
Comment 1 Fabian Deutsch 2014-12-15 10:35:08 UTC 
Moving this to sos, as it seems to be a generic traceback if that path is not mounted/existant.
Comment 3 Bryn M. Reeves 2014-12-15 13:05:09 UTC 
> 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?
Comment 4 Bryn M. Reeves 2014-12-15 13:09:35 UTC 
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.
Comment 6 Pavel Moravec 2015-03-29 20:02:32 UTC 
Is there a reproducer machine available, please? That would speedup our investigation a lot..
Comment 11 Ying Cui 2015-04-29 10:25:14 UTC 
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.
Comment 12 Pavel Moravec 2015-04-29 10:54:46 UTC 
(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.
Comment 13 Fabian Deutsch 2015-05-04 10:51:39 UTC 
Closing this according to comment 11 and comment 12.
Note You need to log in before you can comment on or make changes to this bug.