Bug 156990 - Apparmor gets started automatically on update
Summary: Apparmor gets started automatically on update
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: AppArmor (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Dominic W Reynolds
QA Contact: Dominic W Reynolds
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 11:25 UTC by Reinhard Max
Modified: 2006-04-03 05:43 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Reinhard Max 2006-03-10 11:25:13 UTC 
After updating from beta3 to beta7 I found that apparmor was running without me having enabled it. It might be OK to enable apparmor on a fresh installation, but it shouldn't be enabled on an update if it wasn't running before.

See the next bug I am going to submit for the reason.
Comment 1 Dominic W Reynolds 2006-03-10 20:43:53 UTC 
This makes sense. Code 10 precursers (SLES9, SL10.1) won't have it enabled by default so we shouldn't change behavior without an explicit user ack during installation. 

We can make the chkconfig changes contingent on a new install rather than upgrade.

For sles9 we will need some special handling as the packages are renamed and obsolete the previous ones (rather than upgrade).
Comment 2 Dominic W Reynolds 2006-03-26 19:07:55 UTC 
Marking this as critical rather than blocker. The related profile problems for mail have been adressed.
Comment 3 Dominic W Reynolds 2006-04-03 05:43:26 UTC 
Fixed. Checked into autobuild.