Bug 116749 - apparmor modules are configured as autoyast enabled but they are not
Summary: apparmor modules are configured as autoyast enabled but they are not
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: AppArmor (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dominic W Reynolds
QA Contact: Keiran Haggerty
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-13 12:47 UTC by Uwe Gansert
Modified: 2006-01-29 15:18 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 Uwe Gansert 2005-09-13 12:47:27 UTC 
the apparmor yast modules have:

X-SuSE-YaST-AutoInstClonable=true
X-SuSE-YaST-AutoInst=all

in their config files but they are not autoyast enabled. There is no *_auto.ycp
client for them.
In RC2 you can choose to configure the modules in the autoyast UI now but the
yast-client for the autoinstallation setup can't be started.
Comment 1 Marcus Meissner 2005-09-13 12:51:39 UTC 
We need to fix this via YOU update I think, it might be too late for 10.0 now.
Comment 2 Uwe Gansert 2005-09-13 13:25:53 UTC 
fixed that for RC3
Comment 3 Uwe Gansert 2006-01-20 14:49:30 UTC 
you did it again in 10.1
Comment 4 Steve Beattie 2006-01-29 15:18:34 UTC 
I think I've disabled it in a fix (all->none, true->false, for the two options listed in the original description) committed for beta 3 (and in our local svn tree, so it shouldn't reoccur again). The real solution is to allocate some resources to write *_auto.ycp for the apparmor stuff.

Thanks.