From Fedora Project Wiki

Revision as of 10:26, 11 December 2012 by Psklenar (talk | contribs) (more Prerequisite, selinux test case added)

Fedora Test Days

Date 2012-12-12
Time all day

Website QA/Fedora_18_test_days
IRC #fedora-test-day (webirc)
Mailing list test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on FirewallD

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

1. * Installed Fedora 18 Beta with latest updates. It is possible to convert the LiveCD into LiveUSB by following the How_to_create_and_use_Live_USB instructions.

Make sure you have all current updates (and temporal fixes) installed by:

# yum update

Clear your audit log (especially important in case you aren't running from the live medium):

# echo -n > /var/log/audit/audit.log

2. Packages firewalld, firewall-config (Test case 5) and firewall-applet (Test case 6) installed.

# yum install firewalld firewall-config firewall-applet 

3. Disable and stop iptables, ip6tables and ebtables services:

 systemctl disable iptables.service
 systemctl stop iptables.service
 systemctl disable ip6tables.service
 systemctl stop ip6tables.service
 systemctl disable ebtables.service
 systemctl stop ebtables.service

4. Make sure that the services are not running anymore

 systemctl status iptables.service
 systemctl status ip6tables.service
 systemctl status ebtables.service

Test Cases

Optional Tests and Test Packages

Test Results

If you have problems with any of the tests, report a bug to Bugzilla. For instance file a bug report against the component firewalld if you have problems testing firewlld. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

Test Matrix

User Firewalld usable and active FirewallD and NetworkManager Persistent changes of firewall zones Runtime changes of firewall zones firewall-config firewall-applet system-config-printer selinux-AVCs References
Sample User
Pass pass
Pass pass
Warning warn
Fail fail
  1. Test 3.1 failed RHBZ #54321 (firewall-cmd --list-all failed with an error)
  2. RHBZ #12345