Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1673625

Summary: All firewalld operations failing since Fedora-Rawhide-20190203.n.0
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: firewalldAssignee: Eric Garver <egarver>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: egarver, jpopelka, twoerner
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: openqa
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 17:22:04 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:
Bug Depends On:    
Bug Blocks: 1574713    

Description Adam Williamson 2019-02-07 16:11:11 UTC 
Since Fedora-Rawhide-20190203.n.0 , all firewalld operations seem to be broken. All openQA tests that do something with firewalld are reliably failing.

`firewall-cmd --state` shows "failed" and returns 251. `systemctl status firewalld.service` shows "active (running)", but the logs show multiple errors:

Feb 07 07:29:48 adam.happyassassin.net firewalld[1181]: ERROR: '/usr/sbin/ebtables-restore --noflush' failed: Bad table name 'nat'.
Feb 07 07:29:48 adam.happyassassin.net firewalld[1181]: ERROR: '/usr/sbin/ebtables-restore --noflush' failed: Bad table name 'nat'.
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: COMMAND_FAILED: '/usr/sbin/ebtables-restore --noflush' failed: Bad table name 'nat'.
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore: line 4 failed
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: '/usr/sbin/ip6tables-restore -w -n' failed: ip6tables-restore: line 11 failed
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: COMMAND_FAILED: '/usr/sbin/ip6tables-restore -w -n' failed: ip6tables-restore: line 11 failed
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore: line 4 failed
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: '/usr/sbin/ip6tables-restore -w -n' failed: ip6tables-restore: line 4 failed
Feb 07 07:29:50 adam.happyassassin.net firewalld[1181]: ERROR: COMMAND_FAILED: '/usr/sbin/ip6tables-restore -w -n' failed: ip6tables-restore: line 4 failed

Commands like `firewall-cmd --permanent --add-service postgresql` show "Error: INVALID_ZONE".

Proposing as a Beta blocker as a violation of "After system installation without explicit firewall configuration, the system firewall must be active on all non-loopback interfaces. The only ports which may be open to incoming traffic are port 22 (ssh) and port 9090 (Cockpit web interface). Supported install-time firewall configuration options must work correctly" - https://fedoraproject.org/wiki/Basic_Release_Criteria#Firewall_configuration
Comment 1 Eric Garver 2019-02-07 17:22:04 UTC 

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