1400478 – firewalld writes ifcfg backup files with wrong extension .old

Bug 1400478 - firewalld writes ifcfg backup files with wrong extension .old

Summary: firewalld writes ifcfg backup files with wrong extension .old

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	firewalld
Sub Component:
Version:	7.3
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Thomas Woerner
QA Contact:	Tomas Dolezal
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2016-12-01 10:38 UTC by Beniamino Galvani
Modified:	2017-08-01 16:22 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-08-01 16:22:56 UTC
Target Upstream Version:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:1934	0	normal	SHIPPED_LIVE	firewalld bug fix and enhancement update	2017-08-01 17:55:15 UTC

Description Beniamino Galvani 2016-12-01 10:38:51 UTC

Version: firewalld-0.4.3.2-8.el7.noarch

When doing a backup of a ifcfg file, firewalld creates a new file with
the .old extension, which is not ignored by NetworkManager and is
considered as a new, duplicate connection.

Probably the following commit should be backported:

https://github.com/t-woerner/firewalld/commit/fe6cf16e5a5ef3e49cdb554af8cf18024371554a

Steps to reproduce:

 # firewall-cmd --permanent --zone=external --add-interface=ens8
 A new file 'ifcfg-ens8.old' is created in /etc/sysconfig/network-scripts/

Comment 6 errata-xmlrpc 2017-08-01 16:22:56 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://access.redhat.com/errata/RHBA-2017:1934

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