Bug 1743665

Summary:	[nmstate] A new profile is created instead of editing the existing inactive one
Product:	Red Hat Enterprise Linux 8	Reporter:	Michael Burman <mburman>
Component:	nmstate	Assignee:	Fernando F. Mancera <ferferna>
Status:	CLOSED ERRATA	QA Contact:	Mingyu Shi <mshi>
Severity:	high	Docs Contact:
Priority:	high
Version:	8.1	CC:	dholler, edwardh, ferferna, jiji, jishi, network-qe, till
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:00:06 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:

Description Michael Burman 2019-08-20 12:26:51 UTC

Description of problem:
[nmstate] A new profile is created instead of editing the existing inactive one  

I have a physical interface that is inactive. I'm editing it using nmstate and an additional profile is created instead using the one that is already exist.
 
Version-Release number of selected component (if applicable):
nmstate-0.0.8-3.el8.noarch
Red Hat Enterprise Linux release 8.1 Beta (Ootpa)
kernel-4.18.0-107.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Have a physical NIC, inactive - ifcfg-enp2s0f2
2. Edit it via nmstate - nmstatectl edit enp2s0f2 and change state to up

Actual results:
new profile is created ifcfg-enp2s0f2-1

Expected results:
Should be only one profile

Comment 1 Dominik Holler 2019-11-18 06:57:42 UTC

tracked by https://nmstate.atlassian.net/browse/NMSTATE-267

Comment 2 Dominik Holler 2019-12-06 16:23:21 UTC

Fernando, can this bug changed already to MODIFIED?

Comment 3 Fernando F. Mancera 2019-12-06 18:55:30 UTC

Hi,

yes, this bug can be changed to MODIFIED.

Thanks.

Comment 9 errata-xmlrpc 2020-04-28 16:00:06 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-2020:1696