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 1313023 - command "systemctl reload firewalld" stops firewalld
Summary: command "systemctl reload firewalld" stops firewalld
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.2
Hardware: noarch
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-29 18:35 UTC by Richard D Alloway
Modified: 2016-11-03 21:02 UTC (History)
2 users (show)

Fixed In Version: firewalld-0.4.2-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 21:02:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch which resolves this bug (737 bytes, patch)
2016-02-29 18:49 UTC, Richard D Alloway 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
CentOS 9054 0 None None None 2016-02-29 18:35:17 UTC
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 Richard D Alloway 2016-02-29 18:35:18 UTC 
Description of problem:
Original bug reporter submitted:  
I've noticed a very strange behaviour which resulted in me not having a firewall running for quite a few hours. 
If I run:
"systemctl reload firewalld"
firewalld stops instead of being reloaded.
The console doesn't return a message and it all looks like the reload action is carried out successfully.
Indeed, my earlier command had stopped firewalld altogether!
I've reproduced this behaviour all the time.

Version-Release number of selected component (if applicable):
7.1-1503, 7.2-1511

How reproducible:
Always

Steps to Reproduce:
1. Check firewalld is running with "systemctl status firewalld". Result: active
2. Run "systemctl reload firewalld"
3. Check firewalld is running with "systemctl status firewalld". Result: active
4. Run "systemctl reload firewalld"
5. Check status with "systemctl status firewalld". Result is: inactive

Actual results:
firewalld exits after the 2nd SIGHUP because the signal handler is not set back up after the 1st time it is handled

Expected results:
Upon SIGHUP, firewalld should execute the firewall reload and set the SIGHUP signal handler back up 

Additional info:
I resolved this issue within the CentOS Bug Tracker under bug 9054 (https://bugs.centos.org/view.php?id=9054) and was told I needed to submit the bug and fix here.
Comment 2 Richard D Alloway 2016-02-29 18:49:45 UTC 
Created attachment 1131667 [details]
Proposed patch which resolves this bug
Comment 3 Thomas Woerner 2016-04-12 14:44:24 UTC 
This has been fixed upstream: https://github.com/t-woerner/firewalld/commit/0912fc66fbfe81007a00ff2b453cf83bc880a245
Comment 9 errata-xmlrpc 2016-11-03 21:02:36 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.