-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
Deleting OVN networks fail in a clustered environment #709
Comments
In a clean environment trying to create ovn networks and delete them...
|
I've got that one reproduced locally, it didn't trip our testing due to automated testing only running on single-chassis deployments... |
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Apr 1, 2024
This case happens when a network was deleted by the cluster leader but some other servers in the cluster are yet to stop the network and remove themselves as chassis in the HA group. Closes lxc#709 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
The fix for this one is now in the zabbly stable repository. |
Thank you! I saw a short while ago that it was in zabbly stable and can confirm all is working as expected. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I'm using 0.7.0 of Incus from the Zabbly apt repo alongside the microovn snap in a 3 node cluster environment.
The issue I'm seeing is that I cannot cleanly delete an OVN network. The general error message is of the form:
failed to notify peer 10.20.30.3:8443: Failed deleting OVS chassis "f11" from chassis group "incus-net28": object not found
The network is no longer listed in the northbound, but the incus database still has a listing for the network and can't be deleted without modifying the db manually.
The text was updated successfully, but these errors were encountered: