Bug 795831 - AVC subtest provide incorrect results on RHEL7
Summary: AVC subtest provide incorrect results on RHEL7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
: 797177 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 15:53 UTC by Ondrej Hudlicky
Modified: 2019-05-22 13:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 08:06:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Ondrej Hudlicky 2012-02-21 15:53:18 UTC
Description of problem:
Seems that *AVC subtest* looks for audit messages generated
also before the test case run. As a results after first AVC denial all
following AVC checks fail.

Version-Release number of selected component (if applicable):
https://beaker-stage.engineering.redhat.com/jobs/12589

How reproducible:
always

Actual results:
each *-avc.log contain all AVC denial messages

Expected results:
each *-avc.log contain just AVCs reported during test case run

Additional info:
Blocks RHEL7 Alpha-1 testing

Comment 1 Bill Peck 2012-02-21 16:13:23 UTC
Marian,

Let me know if there is anything you need for this.  Systems are available on beaker-stage to reproduce this.

Comment 2 Bill Peck 2012-02-21 18:17:41 UTC
This is an interesting bug, but as far as I can tell beah/rhts is doing everything correctly.  Here is what is happening..

1 - Hardware clock is off by one hour or so.
2 - System boots and spews some selinux errors that are in the "future"
3 - ntpd starts and resets the time back to the correct time slot
4 - beah runs and does ausearch using correct start time and is picking up those boot up errors until we progress past the corrected time offset.

I was able to "fix" this by setting the systems hardware clock to the current time and then re-running the test.  

Interestingly the original selinux error is no where to be found now since it happened before we started testing.   So its good that this happened and means we should probably have the install task or some other task check for selinux errors from before we ran.

I'm going to close this as "not a bug".

Thanks!

Comment 4 Bill Peck 2012-07-17 13:47:17 UTC
*** Bug 797177 has been marked as a duplicate of this bug. ***

Comment 5 Bill Peck 2012-07-23 18:45:13 UTC
http://gerrit.beaker-project.org/#/c/1235/

Comment 6 Dan Callaghan 2012-08-09 08:06:48 UTC
Beaker 0.9.2 has been released.


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