Skip to content
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

OVN network connected to uplink with no ipv4.address or ipv6.address results in "Not found" on info/delete #1062

Closed
stgraber opened this issue Jul 31, 2024 · 0 comments · Fixed by #1063
Assignees
Labels
Bug Confirmed to be a bug Easy Good for new contributors
Milestone

Comments

@stgraber
Copy link
Member

It was reported that an uplink network with just an "ipv4.ovn.ranges" configured but no "ipv4.address" can be used as an uplink network for an OVN network (that's fine) but that then trying to use "network info" or "network delete" on that OVN network fails with "not found".

We should either make it a hard requirement that IPv4 or IPv6 connectivity is configured on the uplink before it can be used (may be the most user friendly option). Or allow the use of an uplink with neither protocol but still make sure the various entries are created so it can be deleted.

@stgraber stgraber added Bug Confirmed to be a bug Easy Good for new contributors labels Jul 31, 2024
@stgraber stgraber self-assigned this Jul 31, 2024
@stgraber stgraber added this to the incus-6.4 milestone Jul 31, 2024
stgraber added a commit to stgraber/incus that referenced this issue Aug 1, 2024
@hallyn hallyn closed this as completed in 42b5f40 Aug 1, 2024
stgraber added a commit that referenced this issue Aug 4, 2024
Closes #1062

Signed-off-by: Stéphane Graber <[email protected]>
Sponsored-by: Luizalabs (https://luizalabs.com)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Confirmed to be a bug Easy Good for new contributors
Development

Successfully merging a pull request may close this issue.

1 participant