Bug 1113630

Summary:	[RFE] indicate vNICs that are out-of-sync from their configuration on engine
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	GenadiC <gcheresh>
Component:	ovirt-engine	Assignee:	eraviv
Status:	CLOSED ERRATA	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5.0	CC:	bugs, danken, dholler, emarcus, eraviv, lsurette, mburman, mgoldboi, mkalinin, mperina, mtessun, srevivo
Target Milestone:	ovirt-4.4.6	Keywords:	FutureFeature
Target Release:	4.4.6
Hardware:	x86_64
OS:	Linux
Whiteboard:	sync-to-jira
Fixed In Version:	ovirt-engine-4.4.6.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1848986 (view as bug list)		Environment:
Last Closed:	2021-06-01 13:22:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1621421, 1676708, 1719464, 1766414, 1848986, 1952057, 1952353
Bug Blocks:

Description GenadiC 2014-06-26 14:13:42 UTC

Description of problem:
If you configure custom properties on the VNIC profile or if you configure QOS for it, the update of the VNIC profile will happen only after you unplug/plug VNIC or restart the VM.
So there should be a way to inform user that that VNIC profile is not synced if restart didn't happen yet

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Add VNIC profile to specific VNIC
2. Update it with security group custom properties or QOS
3. Make sure the update didn't happen yet

Actual results:
The VNIC profile shows that it is updated

Expected results:
The VNIC profile should show that it is not actually updated - by unsynced

Additional info:

Comment 3 Michal Skrivanek 2020-03-19 15:41:44 UTC

We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.

Comment 4 Dominik Holler 2020-03-23 14:26:30 UTC

Let's keep this RFE open, because I think it would be really helpful for the user.

Comment 6 Michal Skrivanek 2020-06-23 12:34:51 UTC

This request is not currently committed to 4.4.z, moving it to 4.5

Comment 7 Dominik Holler 2020-11-20 07:41:22 UTC

On the update of network filter or network filter parameters in Engine, we can check if we can just update them on the running VM instance.
This idea is tracked in bug #1899583 .

Comment 8 Michal Skrivanek 2021-04-07 12:24:48 UTC

*** Bug 1719464 has been marked as a duplicate of this bug. ***

Comment 10 Michael Burman 2021-04-21 12:51:19 UTC

Verified on - rhvm-4.4.6.5-447.gd80dda7.9.el8ev.noarch

out-of-sync icon will be triggered on VM's view and in the network interfaces sub tab of the VM for the next properties change:
- VM QoS
- MTU
- network filter
- Sr-IOV failover network

Gap:
- VLAN should be fixed with BZ 1952057

Comment 14 errata-xmlrpc 2021-06-01 13:22:09 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 (Moderate: RHV Manager security update (ovirt-engine) [ovirt-4.4.6]), 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/RHSA-2021:2179