Commit 3dc31b37 authored by anonym's avatar anonym
Browse files

Disable printk rate limiting when monitoring the AppArmor log.

The rate limiting can otherwise drop the entries we're looking for,
which makes our tests incorrect. This is recommended on the AppArmor
wiki: http://wiki.apparmor.net/index.php/AppArmorMonitoring

Will-fix: #9924
parent 5cb5daf4
......@@ -1122,6 +1122,9 @@ end
Given /^I (?:re)?start monitoring the AppArmor log of "([^"]+)"$/ do |profile|
next if @skip_steps_while_restoring_background
# AppArmor log entries may be dropped if printk rate limiting is
# enabled.
@vm.execute_successfully('sysctl -w kernel.printk_ratelimit=0')
# We will only care about entries for this profile from this time
# and on.
guest_time = DateTime.parse(@vm.execute_successfully('date').stdout)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment