Bug 1480647 - RFC: setroubleshootd crashing with error: ValueError: list modified during sort
RFC: setroubleshootd crashing with error: ValueError: list modified during sort
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: setroubleshoot (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Miroslav Grepl
BaseOS QE Security Team
Depends On:
  Show dependency treegraph
Reported: 2017-08-11 10:55 EDT by Paulo Andrade
Modified: 2017-08-21 07:14 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-15 13:51:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paulo Andrade 2017-08-11 10:55:15 EDT
Backtrace is:

:analyze.py:307:prune:ValueError: list modified during sort
:Traceback (most recent call last):
:  File "/usr/lib64/python2.6/atexit.py", line 24, in _run_exitfuncs
:    func(*targs, **kargs)
:  File "/usr/lib64/python2.6/site-packages/setroubleshoot/server.py", line 547, in goodbye
:    database.save()
:  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 377, in save
:    self.prune()
:  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 307, in prune
:    self.sigs.signature_list.sort(lambda a,b: cmp(a.last_seen_date, b.last_seen_date))
:ValueError: list modified during sort
:Local variables in innermost frame:
:self: <setroubleshoot.analyze.SETroubleshootDatabase object at 0x1042b10>

  My guess is that it is receiving a SIGHUP during exit,
causing the list to be reset.

  I found one extra similar report, but never resolved, at:
[[abrt] setroubleshoot-server: analyze.py:283:prune:ValueError: list modified during sort]

  Unless I am missing some other condition where the list may
change during sort, I believe the fix is likely to block SIGHUP
during exit, as there is no point in rereading config files if
Comment 3 Petr Lautrbach 2017-08-21 07:14:09 EDT
This bug is reported on Red Hat Enterprise Linux 6 but it seems to be a problem of Red Hat Enterprise Linux 7. There's already a similar bug for this - https://bugzilla.redhat.com/show_bug.cgi?id=1315241 - lets move the discussion there.

Note You need to log in before you can comment on or make changes to this bug.