Bug 1566673

Summary:	Access to network setup, caps and numvfs change is not synced
Product:	[oVirt] vdsm	Reporter:	Edward Haas <edwardh>
Component:	Core	Assignee:	Edward Haas <edwardh>
Status:	CLOSED WONTFIX	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.30.0	CC:	bugs, danken, phoracek
Target Milestone:	---	Flags:	sbonazzo: ovirt-4.3-
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-03 10:31:44 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:

Description Edward Haas 2018-04-12 18:43:56 UTC

Description of problem:
Performing host network changes or querying during changes in parallel may result in either corruption of the configuration or in presenting a state of the host in a intermediate unstable changing state.
Although the caller is expected to protect against such access, it is the responsibility of VDSM networking API to protect itself, providing a safe way to set or get the host network configuration.

Expected results:
Host network state changes and queries verbs should be in sync, not allowing concurrent access.

It is suggested to softly block on these verbs.

Comment 1 Dan Kenigsberg 2018-09-03 10:31:44 UTC

Engine makes sure not to shoot a getCaps while setupNetwork is on the fly.

It is not a high priority to protect this also on Vdsm.