You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user might provide his/her own libvirt network and attach the domain to it via its XML configuration.
In such cases, the Context object will have the network resource still set to None. This is due to the fact that the Context Factory is not aware of XML specific configurations.
This lead to bugs in the network based Plugins as they assume the presence of a libvirt network but they cannot reach it.
Possible solutions are:
If no network is specified in the Context's JSON configuration, parse the XML and try to understand if the domain is attached to any network. This is a bit controversial as we try to be as much "libvirt config agnostic" as possible.
Once the domain is created, try to lookup to which network is attached. This solution is simpler but requires libvirt APIs support. Investigation required.
The text was updated successfully, but these errors were encountered:
The user might provide his/her own libvirt network and attach the domain to it via its XML configuration.
In such cases, the Context object will have the network resource still set to None. This is due to the fact that the Context Factory is not aware of XML specific configurations.
This lead to bugs in the network based Plugins as they assume the presence of a libvirt network but they cannot reach it.
Possible solutions are:
The text was updated successfully, but these errors were encountered: