From Fedora Project Wiki

(create test case (split from previous combined Testcase_kickstart_firewall))
 
(add username / password info)
Line 8: Line 8:
# Boot using a dedicated installer image for the Fedora release you wish to test
# Boot using a dedicated installer image for the Fedora release you wish to test
# At the boot menu, edit the options for one of the "Install Fedora" options to include the parameter <tt>inst.ks=http://fedorapeople.org/groups/qa/kickstarts/firewall-disabled-net.ks</tt>
# At the boot menu, edit the options for one of the "Install Fedora" options to include the parameter <tt>inst.ks=http://fedorapeople.org/groups/qa/kickstarts/firewall-disabled-net.ks</tt>
# The installation should run unattended: allow it to complete, boot the installed system, and check the state of the firewall using {{command|sudo iptables -L -v}} (no {{code|REJECT}} rules should be present in the output) or {{command|sudo firewall-cmd --state}} (should report {{code|not running}}), and/or by attempting to connect to a port or running service from the other test system
# The installation should run unattended: allow it to complete, boot the installed system (log in as 'root' with password 'anaconda'), and check the state of the firewall using {{command|sudo iptables -L -v}} (no {{code|REJECT}} rules should be present in the output) or {{command|sudo firewall-cmd --state}} (should report {{code|not running}}), and/or by attempting to connect to a port or running service from the other test system
|results=
|results=
# The firewall should be disabled
# The firewall should be disabled
}}
}}
[[Category:Kickstart_test_cases]]
[[Category:Kickstart_test_cases]]

Revision as of 21:02, 23 March 2016

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#firewall-configuration release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case tests whether disabling the firewall works correctly in a kickstart-driven installation.

Setup

  1. Prepare a test system (virtual or real) with sufficient memory to install Fedora, an empty hard disk (or such that you do not mind losing the contents of all connected hard disks: this test WILL wipe all hard disks connected to the test system), and (ideally) a network connection and another system from which you can connect to the test system

How to test

  1. Boot using a dedicated installer image for the Fedora release you wish to test
  2. At the boot menu, edit the options for one of the "Install Fedora" options to include the parameter inst.ks=http://fedorapeople.org/groups/qa/kickstarts/firewall-disabled-net.ks
  3. The installation should run unattended: allow it to complete, boot the installed system (log in as 'root' with password 'anaconda'), and check the state of the firewall using sudo iptables -L -v (no REJECT rules should be present in the output) or sudo firewall-cmd --state (should report not running), and/or by attempting to connect to a port or running service from the other test system

Expected Results

  1. The firewall should be disabled