Bug 1566673 - Access to network setup, caps and numvfs change is not synced
Summary: Access to network setup, caps and numvfs change is not synced
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.30.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.3.0
: ---
Assignee: Edward Haas
QA Contact: Meni Yakove
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-12 18:43 UTC by Edward Haas
Modified: 2018-09-03 10:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-09-03 10:31:44 UTC
oVirt Team: Network
rule-engine: ovirt-4.3+

Attachments (Terms of Use)

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.

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