Bug 783393 - sealert tracebacks with "ZeroDivisionError: float division"
Summary: sealert tracebacks with "ZeroDivisionError: float division"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: setroubleshoot
Version: 5.8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-20 09:06 UTC by Milos Malik
Modified: 2016-02-11 15:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-24 19:47:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Milos Malik 2012-01-20 09:06:57 UTC
Description of problem:


Version-Release number of selected component (if applicable):
setroubleshoot-plugins-2.0.4-2.el5
setroubleshoot-server-2.0.5-5.el5
setroubleshoot-2.0.5-5.el5

How reproducible:
always

Steps to Reproduce:
# rm -f dummy-audit.log 
# touch dummy-audit.log
# sealert -a dummy-audit.log 
100% doneTraceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/setroubleshoot/analyze.py", line 620, in task
    self.progress = float(self.n_bytes_read) / float(self.file_size)
ZeroDivisionError: float division

  
Actual results:
* a traceback

Expected results:
* no traceback, sealert skips the processing of empty file

Comment 1 Miroslav Grepl 2012-01-23 15:04:11 UTC
We have a fix for this in Fedora/RHEL.

Comment 2 RHEL Program Management 2012-06-12 01:33:02 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.


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