Bug 1423941

Summary:	ipsets cannot be overriden by local config
Product:	Red Hat Enterprise Linux 7	Reporter:	Tomas Dolezal <todoleza>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.3	CC:	todoleza
Target Milestone:	rc	Keywords:	Upstream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 16:22:56 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:

Description Tomas Dolezal 2017-02-17 15:19:46 UTC

Description of problem:
system-default ipset prevents loading of admin-modified ipset with 
ERROR: Failed to load ipset file '/etc/firewalld/ipsets/myipset.xml': NOT_APPLIED: myipset

Version-Release number of selected component (if applicable):
firewalld-0.4.4.3-2.el7.noarch

How reproducible:
always

Steps to Reproduce:
# cat /usr/lib/firewalld/ipsets/myipset.xml
<?xml version="1.0" encoding="utf-8"?>
<ipset type="hash:ip">
  <short>My Ipset</short>
  <description>description</description>
  <entry>1.2.3.4</entry>
  <entry>1.2.3.5</entry>
  <entry>1.2.3.6</entry>
</ipset>
firewall-cmd --reload
firewall-cmd --ipset myipset --add-entry 1.2.3.77
firewall-cmd --runtime-to-permanent
firewall-cmd --reload


Actual results:
before last reload, the .77 ipaddr is present
journal:
ERROR: Failed to load ipset file '/etc/firewalld/ipsets/myipset.xml': NOT_APPLIED: myipset

Expected results:
/etc config overrides

Additional info:

Comment 4 errata-xmlrpc 2017-08-01 16:22:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1934