-
Notifications
You must be signed in to change notification settings - Fork 937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GetNetworkState can't detect bridge interfaces configured with OVS #14606
Labels
Improvement
Improve to current situation
Milestone
Comments
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 21, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 21, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 21, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 21, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 21, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 25, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
tomponline
added a commit
that referenced
this issue
Feb 28, 2025
State was imported only to get some config keys for setting up the OVN command connection arguments. We should try to not import state where possible, and only import the fields we need at the lowest level. This helps not only with reducing the size of imports, but also for use of packages externally, and also for unit testing. This is required for using the OVS package externally. See #15044 and #14606. cc @ghadi-rahme
ghadi-rahme
added a commit
to ghadi-rahme/lxd
that referenced
this issue
Feb 28, 2025
…tion This allows OVS bridge information to be read by LXD. Other applications such as MAAS make use of this function and require the ability to retrieve OVS bridge information. Fixes canonical#14606 Signed-off-by: Ghadi Elie Rahme <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
We are NOT using LXD but rather LXD as a library, see https://github.com/canonical/maas/blob/7265eeecb055e573d8c40e63b3964c46e657bae6/src/host-info/pkg/info/info.go#L192
Issue description
GetNetworkState can't detect a bridge interface configured with OVS.
It returns
Steps to reproduce
GetNetworkState
like in https://github.com/canonical/lxd/blob/main/lxd/resources/network.go#L603-L650The text was updated successfully, but these errors were encountered: