Bug 993650

Summary:	rfe: runtime conf may be saved as permanent
Product:	Red Hat Enterprise Linux 7	Reporter:	Petr Sklenar <psklenar>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	ebenes, jpopelka, jscotka, mvadkert, tlavigne, todoleza
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	firewalld-0.3.9-11.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 13:22:37 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:
Bug Blocks:	980210

Description Petr Sklenar 2013-08-06 11:06:24 UTC

Description of problem:
runtime conf may be saved as permanent

Version-Release number of selected component (if applicable):
firewalld-0.3.4-1.fc19.noarch

How reproducible:
that's rfe

Steps to Reproduce:
1. firewall-config
2. do whatever actions during "runtime configuration"
3. now you want to do the some for permanent

Actual results:
not possible => manually switching between runtime X permanent

Expected results:
some action like: "copy current runtime configuration to permanent"

Additional info:

Comment 3 Jiri Popelka 2013-08-16 10:48:27 UTC

Already existing idea (bug #910491).

Comment 7 Thomas Woerner 2014-09-29 20:59:34 UTC

Fixed upstream:

https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=6b9867cd5c5e2c83adeec42666521a420e59ef11

and 

https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=735fa38bd9e49945656dd8b44ee60bb962196b6d

Comment 9 Jiri Popelka 2014-10-14 16:42:54 UTC

Thomas, the following upstream commits should be included too:

48c5d6c
54f1ce6
987433d
a5d73a5
ed6327c
512b30e

Comment 13 errata-xmlrpc 2015-03-05 13:22:37 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/RHBA-2015-0520.html