Bug 1246539
Summary: | abrt misses a dependency on python-argparse | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | James Boyle <unixi> |
Component: | abrt | Assignee: | Jakub Filak <jfilak> |
Status: | CLOSED ERRATA | QA Contact: | Martin Kyral <mkyral> |
Severity: | high | Docs Contact: | Lenka Špačková <lkuprova> |
Priority: | high | ||
Version: | 6.8 | CC: | ayadav, fkrska, jberan, jfilak, joshua.jordan, kfiresmith, kwalker, mhabrnal, mkyral, mpatocka, nobody, pablo.iranzo, pmoravec, unixi, xavier |
Target Milestone: | rc | Keywords: | EasyFix, Regression, Reproducer |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | abrt-2.0.8-36.el6 | Doc Type: | Bug Fix |
Doc Text: |
_abrt_ no longer missing a dependency on _python-argparse_
A previously missing dependency of the _abrt_ packages on the _python-argparse_ package resulting in errors like "ImportError: No module named argparse" has been fixed. This problem usually occurred if customers upgraded from an earlier version of Red Hat Enterprise Linux, or during a fresh installation if customers removed the _nfs-utils_ or _ipa-client_ packages.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-11 00:38:06 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: | 1254457 |
Description
James Boyle
2015-07-24 14:13:24 UTC
Thank you for the report! abrt-action-generate-machine-id crashes because abrt package misses a dependency on python-argparse. abrt-dump-oops triggers abrt-action-generate-machine-id, therefore I think that abrt-dump-oops runs continuously for some other reason. Please install that package: # yum install python-argparse and run the following command: # /usr/libexec/abrt-action-generate-machine-id to verify that the crash is fixed. Please attach the result of the following command as well: # cat /var/log/messages | grep abrt Installing python-argparse fixes the error, but why was the dependency not installed in the first place? I can verify the /usr/libexec/abrt-action-generate-machine-id works and returns info from dmidecode. grep abrt /var/log/messages is far too long to list entirely, but here is a sample: Jul 23 08:43:33 host abrt: detected unhandled Python exception in '/usr/libexec/abrt-action-generate-machine-id' Jul 23 08:43:33 host abrt-server[18907]: Saved Python crash dump of pid 18906 to /var/spool/abrt/pyhook-2015-07-23-08:43:33-18906 Jul 23 08:43:33 host abrtd: Directory 'pyhook-2015-07-23-08:43:33-18906' creation detected Jul 23 08:43:33 host abrtd: Duplicate: core backtrace Jul 23 08:43:33 host abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-08:43:33-18906 Jul 23 08:43:33 host abrtd: Deleting problem directory pyhook-2015-07-23-08:43:22-18675 (dup of pyhook-2015-07-23-08:43:33-18906) Jul 23 08:43:33 host abrtd: Sending an email... Jul 23 08:43:33 host abrtd: Email was sent to: root@localhost Jul 23 08:43:33 host abrtd: Duplicate: core backtrace Jul 23 08:43:33 host abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-03:59:32-5493 Jul 23 08:43:33 host abrtd: Deleting problem directory pyhook-2015-07-23-08:43:22-18687 (dup of pyhook-2015-07-23-03:59:32-5493) Jul 23 08:43:33 host abrt: detected unhandled Python exception in '/usr/bin/abrt-action-notify' Jul 23 08:43:34 host abrt-server[18918]: Saved Python crash dump of pid 18917 to /var/spool/abrt/pyhook-2015-07-23-08:43:34-18917 Jul 23 08:43:34 host abrtd: Directory 'pyhook-2015-07-23-08:43:34-18917' creation detected Jul 23 08:43:34 host abrtd: Traceback (most recent call last): Jul 23 08:43:34 host abrtd: File "/usr/bin/abrt-action-notify", line 18, in <module> Jul 23 08:43:34 host abrtd: from argparse import ArgumentParser Jul 23 08:43:34 host abrtd: ImportError: No module named argparse Jul 23 08:43:44 host abrt: detected unhandled Python exception in '/usr/libexec/abrt-action-generate-machine-id' Jul 23 08:43:44 host abrt-server[19154]: Saved Python crash dump of pid 19153 to /var/spool/abrt/pyhook-2015-07-23-08:43:44-19153 Jul 23 08:43:44 host abrtd: Directory 'pyhook-2015-07-23-08:43:44-19153' creation detected Jul 23 08:43:44 host abrtd: Duplicate: core backtrace Jul 23 08:43:44 host abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-08:43:44-19153 Jul 23 08:43:44 host abrtd: Deleting problem directory pyhook-2015-07-23-08:43:33-18906 (dup of pyhook-2015-07-23-08:43:44-19153) Jul 23 08:43:44 host abrtd: Sending an email... Jul 23 08:43:44 host abrtd: Email was sent to: root@localhost Jul 23 08:43:44 host abrtd: Duplicate: core backtrace Jul 23 08:43:44 host abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-03:59:32-5493 Jul 23 08:43:44 host abrtd: Deleting problem directory pyhook-2015-07-23-08:43:34-18917 (dup of pyhook-2015-07-23-03:59:32-5493) Jul 23 08:43:44 host abrt: detected unhandled Python exception in '/usr/bin/abrt-action-notify' Jul 23 08:43:45 host abrtd: Directory 'pyhook-2015-07-23-08:43:45-19165' creation detected Jul 23 08:43:45 host abrt-server[19166]: Saved Python crash dump of pid 19165 to /var/spool/abrt/pyhook-2015-07-23-08:43:45-19165 Jul 23 08:43:45 host abrtd: Traceback (most recent call last): Jul 23 08:43:45 host abrtd: File "/usr/bin/abrt-action-notify", line 18, in <module> Jul 23 08:43:45 host abrtd: from argparse import ArgumentParser Jul 23 08:43:45 host abrtd: ImportError: No module named argparse Jul 23 08:43:56 host abrt: detected unhandled Python exception in '/usr/libexec/abrt-action-generate-machine-id' Jul 23 08:43:56 host abrtd: Directory 'pyhook-2015-07-23-08:43:56-19384' creation detected Jul 23 08:43:56 host abrt-server[19385]: Saved Python crash dump of pid 19384 to /var/spool/abrt/pyhook-2015-07-23-08:43:56-19384 Jul 23 08:43:56 host abrtd: Duplicate: core backtrace Jul 23 08:43:56 host abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-08:43:56-19384 Jul 23 08:43:56 host abrtd: Deleting problem directory pyhook-2015-07-23-08:43:44-19153 (dup of pyhook-2015-07-23-08:43:56-19384) Jul 23 08:43:56 host abrtd: Sending an email... Jul 23 08:43:56 host abrtd: Email was sent to: root@localhost Jul 23 08:43:56 host abrtd: Duplicate: core backtrace Jul 23 08:43:56 host abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-03:59:32-5493 Jul 23 08:43:56 host abrtd: Deleting problem directory pyhook-2015-07-23-08:43:45-19165 (dup of pyhook-2015-07-23-03:59:32-5493) Jul 23 08:43:56 host abrt: detected unhandled Python exception in '/usr/bin/abrt-action-notify' Jul 23 08:43:56 host abrt-server[19397]: Saved Python crash dump of pid 19396 to /var/spool/abrt/pyhook-2015-07-23-08:43:56-19396 Jul 23 08:43:56 host abrtd: Directory 'pyhook-2015-07-23-08:43:56-19396' creation detected Jul 23 08:43:56 host abrtd: Traceback (most recent call last): Jul 23 08:43:56 host abrtd: File "/usr/bin/abrt-action-notify", line 18, in <module> Jul 23 08:43:56 host abrtd: from argparse import ArgumentParser Jul 23 08:43:56 host abrtd: ImportError: No module named argparse (In reply to James Boyle from comment #3) > Installing python-argparse fixes the error, but why was the dependency not > installed in the first place? > Because I forgot to add "Requires: python-argparse" to abrt's spec file. What type of installation did you chose? I installed RHEL-6.7 Workstation on my VM and python-argparse was pulled in as a dependency of nfs-utils and ipa-client. /var/log/messages lines look ok. How did you find out that abrt-dump-oops runs continuously? (In reply to Jakub Filak from comment #4) > (In reply to James Boyle from comment #3) > Because I forgot to add "Requires: python-argparse" to abrt's spec file. > Honestly - this makes me feel better! I didn't want to have to consider other possibilities of why the package might not have been there (other admin, intrusion, etc.). :^) > What type of installation did you chose? I installed RHEL-6.7 Workstation on > my VM and python-argparse was pulled in as a dependency of nfs-utils and > ipa-client. > This was a server installation from RHEL 6.5 (or earlier) that has been patched to current along the way. It aims to be FISMA compliant and in line with that, the general rule is to have the bare minimum installed that's required to get the job done. (things like nfs are not installed at all on this system) > /var/log/messages lines look ok. How did you find out that abrt-dump-oops > runs continuously? 'ps auxwww |grep abrt' showed me that abrt-dump-oops is/was running. Maybe it's supposed to be running all the time (looking at some other systems now, I'm sure it was supposed to be). I could have stated my issue better as, given previous conditions, it seems like a race condition: [scan spool for crashes] -> [crash yourself trying to make the report] -> [email] -> [repeat] ... Anyway, my biggest issue was that my inbox was flooded. I appreciate your help! Thank you, --James I also noticed the missing dep on a minimal server install in my infra as well - after seeing 9k traceback emails in root mail. I'll be filing a support ticket with Red Hat support services to see about getting a new version of this released asap. In the mean time I'll add python-argparse to our server baseline via Puppet. (In reply to James Boyle from comment #5) > > This was a server installation from RHEL 6.5 (or earlier) So the issue has started appearing after you upgraded to RHEL-6.7 > > /var/log/messages lines look ok. How did you find out that abrt-dump-oops > > runs continuously? > > 'ps auxwww |grep abrt' showed me that abrt-dump-oops is/was running. Maybe > it's supposed to be running all the time (looking at some other systems now, > I'm sure it was supposed to be). Your assumptions is correct, abrt-dump-oops watches /var/log/messages for kernel stack traces and converts them to ABRT problem records. *** Bug 1256107 has been marked as a duplicate of this bug. *** Fixed in the rhel-6.8 staging branch. *** Bug 1292909 has been marked as a duplicate of this bug. *** It is important to note that users could have also experienced this issue from a fresh installation if they removed nfs-utils or ipa-client. In some environments and compliance situations only the absolute bare minimum of installed software is allowed, so administrators will remove nfs-utils if the system is not expected to mount NFS volumes. 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://rhn.redhat.com/errata/RHBA-2016-0920.html |