Bug 1722979 - Disabling firewall via kickstart fails
Summary: Disabling firewall via kickstart fails
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks: F31BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2019-06-21 21:58 UTC by Adam Williamson
Modified: 2019-07-15 15:57 UTC (History)
8 users (show)

Fixed In Version: anaconda-31.18-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-15 15:57:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2019-06-21 21:58:04 UTC
openQA has a test which checks that a kickstart install that disables the firewall works. In Fedora-Rawhide-20190621.n.0, it didn't.

The test runs a kickstart install with http://fedorapeople.org/groups/qa/kickstarts/firewall-disabled-net.ks , which has a line:

firewall --disabled

the install runs successfully, but when the test checks whether the firewall is running, it is:

https://openqa.fedoraproject.org/tests/414596#step/firewall_disabled/4

note the state shown is 'running'. It shouldn't be.

This last worked in 20190604.n.0. In 20190609.n.1 the test failed earlier because of https://bugzilla.redhat.com/show_bug.cgi?id=1719057 , and there were no composes between 20190609.n.1 and 20190621.n.0. Proposing as a Beta blocker per basic criterion "...Supported install-time firewall configuration options must work correctly" - https://fedoraproject.org/wiki/Basic_Release_Criteria#Firewall_configuration

Comment 1 Martin Kolman 2019-06-24 20:24:38 UTC
PR: https://github.com/rhinstaller/anaconda/pull/2027

Comment 2 Stephen Gallagher 2019-07-15 13:18:30 UTC
+1 blocker

Comment 3 Adam Williamson 2019-07-15 15:57:33 UTC
oh, this was fixed a while back, test has been passing since.


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