Editing Test Day:2012-12-12 Network Manager and FirewallD

{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_18_test_days]]
| caption = [[FirewallD]]
| date = 2012-12-12
| time = all day
| website = [[QA/Fedora_18_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
}}

{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|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 ...
* Development - [[User:twoerner|Thomas Woerner (twoerner on FreeNode)]]
* Development - [[User:jpopelka|Jiri Popelka (jpopelka on FreeNode)]]
* Development (Network Manager) - [[User:Pavlix|Pavel Šimerda (pavlix on FreeNode)]]
* Quality Assurance - [[User:psklenar|Petr Sklenar (psklenar on FreeNode)]]
* Quality Assurance - [[User:Martix|Martin Holec (Martix on FreeNode)]]

== Prerequisite for Test Day == 

1.  * Installed [http://fedoraproject.org/get-prerelease 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:
<pre># yum update</pre>

Clear your audit log (especially important in case you aren't running from the live medium):
<pre># echo -n > /var/log/audit/audit.log</pre>

2. Packages firewalld, firewall-config (Test case 5) and firewall-applet (Test case 6) installed.
<pre># yum install firewalld firewall-config firewall-applet </pre>

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 ==

* Test case 1: [[QA:Testcase_firewalld_active|Firewalld usable and active]]
* Test case 2: [[QA:Testcase_firewalld_and_NetworkManager|FirewallD and NetworkManager]]
* Test case 3: [[QA:Testcase_persistent_firewalld_zones|Persistent changes of firewall zones]]
* Test case 4: [[QA:Testcase_use_firewalld_zones|Runtime changes of firewall zones]]
* Test case 5: [[QA:Testcase_firewall_config|firewall-config]]
* Test case 6: [[QA:Testcase_firewall-applet|firewall-applet]]
* Test case 7: [[QA:Testcase_system-config-printer|system-config-printer]]
* Test case 8: [[QA:Testcase_selinux-AVCs|selinux-AVCs]]

== Optional Tests ==

* [[QA:Testcase_firewalld_direct|direct interface]]
* [[QA:Testcase_firewalld_with_network_service|initscripts]]

== Test Results ==

If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. For instance file a bug report against the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=firewalld 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 [[Template:result|result template]] to enter your result, as shown in the example result line.

=== Test Matrix ===

{|
! User
! [[QA:Testcase_firewalld_active|Firewalld usable and active]]
! [[QA:Testcase_firewalld_and_NetworkManager|FirewallD and NetworkManager]]
! [[QA:Testcase_persistent_firewalld_zones|Persistent changes of firewall zones]]
! [[QA:Testcase_use_firewalld_zones|Runtime changes of firewall zones]]
! [[QA:Testcase_firewall_config|firewall-config]]
! [[QA:Testcase_firewall-applet|firewall-applet]]
! [[QA:Testcase_system-config-printer|system-config-printer]]
! [[QA:Testcase_selinux-AVCs|selinux-AVCs]]
! References
|-
| [[User:SampleUser|Sample User]]
| {{result|pass}}
| {{result|none}} 
| {{result|pass}}
| {{result|warn}} <ref>Test 3.1 failed {{bz|54321}} (firewall-cmd --list-all failed with an error)</ref>
| {{result|none}}
| {{result|none}}
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|unknown}}
| <references/>
|-
| [[User:luya|Luya Tshimbalanga]]
| {{result|pass}}
| {{result|inprogress}} 
| {{result|inprogress}}
| {{result|inprogress}} 
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:Psklenar|Petr Sklenar]]
| {{result|pass}}
| {{result|warn}} <ref> warn/error in the /var/log/mesasge {{bz|886432}} </ref> 
| {{result|warn}} <ref> {{bz|886459}} {{bz|886461}} </ref>
| {{result|inprogress}} 
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:Mkrizek|Martin Krizek]]
| {{result|pass}}
| {{result|none}}
| {{result|pass}}
| {{result|pass}} 
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|pass}}
| <references/>
|-
|}

== Reference ==
<references/> 
[[Category:Test Days]]