RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1368949 - Trying to get the description for a firewalld zone from command line throws error and prints traceback information.
Summary: Trying to get the description for a firewalld zone from command line throws e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Jan Kepler
URL:
Whiteboard:
Depends On: 1368625
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 08:32 UTC by Thomas Woerner
Modified: 2016-11-03 21:04 UTC (History)
6 users (show)

Fixed In Version: firewalld-0.4.3.2-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1368625
Environment:
Last Closed: 2016-11-03 21:04:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2597 0 normal SHIPPED_LIVE Moderate: firewalld security, bug fix, and enhancement update 2016-11-03 12:11:47 UTC

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


Note You need to log in before you can comment on or make changes to this bug.