Bug 1692188

Summary:	libvirt-5.1.0 with firewalld-0.6.3 - Error: PARSE_ERROR: 'libvirt.xml': rule: Unexpected attribute priority
Product:	[Community] Virtualization Tools	Reporter:	Dennis Schridde <devurandom>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	laine, libvirt-maint, tburke
Target Milestone:	---
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:	2019-03-25 00:27:36 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 Dennis Schridde 2019-03-24 23:26:12 UTC

Description of problem:
# firewall-cmd --check-config
Error: PARSE_ERROR: 'libvirt.xml': rule: Unexpected attribute priority

File /usr/lib/firewalld/zones/libvirt.xml (installed by libvirt) contains:
<rule priority='32767'>
  <reject/>
</rule>

Version-Release number of selected component (if applicable): 5.1.0

How reproducible:
# firewall-cmd --check-config

Steps to Reproduce:
1. # firewall-cmd --check-config

Actual results:
Error: PARSE_ERROR: 'libvirt.xml': rule: Unexpected attribute priority

Expected results:
No errors

Additional info:

Comment 1 Laine Stump 2019-03-25 00:27:36 UTC

This is because your firewalld package isn't new enough to support rule priorities, but when you (or your distro) built the libvirt package, it was configured with "--with-firewalld-zone", which causes the firewalld zonefile /usr/lib/firewalld/zones/libvirt.xml to be installed.

Until your distro has a firewalld that supports rule priorities, you should build the libvirt packages with "configure --without-firewalld-zone ...." (or just remove /usr/lib/firewalld/zones/libvirt.xml to immediately solve the problem on your host (until the next time you update the libvirt packages).


For more details, read the commit log for upstream commits 3b71f2e42 and ae05211a.

Comment 2 Dennis Schridde 2019-03-25 06:50:09 UTC

Thanks for the explanation!  I reported it downstream: https://bugs.gentoo.org/681714