Bug 822290

Summary:	Mechanism for disabling firewall and selinux via kickstart should be re-considered due to firewalld switch
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-17 01:53:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Williamson 2012-05-17 00:21:16 UTC

See also this messy 17 report:

https://bugzilla.redhat.com/show_bug.cgi?id=821966

With Fedora 18 it's very likely the switch to firewalld by default will be back. This might well mean that system-config-firewall-base - which contains lokkit, which anaconda uses to disable firewall/selinux if you specify in a kickstart that they should be disabled - is no longer installed by default.

So we'd either need to move lokkit, or give anaconda a different way to enable/disable the firewall and selinux, or get s-c-f-b back into the default installed package set.

We might also need to teach lokkit how to disable firewalld, but that would seem to be outside the scope of this bug.

Comment 1 Chris Lumens 2012-05-17 01:53:27 UTC


*** This bug has been marked as a duplicate of bug 815540 ***