Bug 1368949

Summary:	Trying to get the description for a firewalld zone from command line throws error and prints traceback information.
Product:	Red Hat Enterprise Linux 7	Reporter:	Thomas Woerner <twoerner>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Jan Kepler <jkejda>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	audrey, extras-qa, jkejda, lmiksik, todoleza, twoerner
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	firewalld-0.4.3.2-6.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1368625	Environment:
Last Closed:	2016-11-03 21:04:21 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:	1368625
Bug Blocks:

Description Thomas Woerner 2016-08-22 08:32:09 UTC

+++ This bug was initially created as a clone of Bug #1368625 +++

Trying to get the description for a zone using firewall-cmd exits with status code 1, and prints an error message:

↪  sudo firewall-cmd --permanent --zone=public --get-description
Traceback (most recent call last):
  File "/bin/firewall-cmd", line 1783, in <module>
    cmd.print_and_exit(settings.getDescription())
NameError: name 'settings' is not defined

The syntax for this command matches the example given in the man page, so this is either a bug in firewall-cmd, or in the way it's packaged. Right?

The equivalent command using the newer CLI utility (`sudo firewallctl zone public get description`) works as it should, however.

I'm testing with firewalld 0.4.3.3, both on Fedora 24 Cloud Base and Fedora 24 Workstation. (Fedora Cloud is a guest in virt-manager 1.4.0 on my host Fedora Workstation desktop.)

--- Additional comment from Thomas Woerner on 2016-08-22 04:28:47 EDT ---

Fixed upstream: https://github.com/t-woerner/firewalld/commit/b67a186b32f832656eefb604b9460f1df5c37a56

Comment 7 errata-xmlrpc 2016-11-03 21:04:21 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://rhn.redhat.com/errata/RHSA-2016-2597.html