fix: pin kube-ovn to 1.13.14 #1347
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cloudnull
approved these changes
Dec 5, 2025
rackerchris
added a commit
to rackerchris/genestack
that referenced
this pull request
Dec 5, 2025
(cherry picked from commit eeb69b1)
cloudnull
pushed a commit
that referenced
this pull request
Dec 5, 2025
dwith
pushed a commit
to dwith/genestack
that referenced
this pull request
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to our friends at KT Cloud, a bug has been identified in kube-ovn > 1.13.14 where when the kube-ovn-controller pods get restarted, acl's are wiped from the ovn databases.
#1342
https://bugs.launchpad.net/neutron/+bug/1939726
This pr pins the version of kube-ovn back to version 1.13.14 until such time as the upstream patches are merged:
kubeovn/kube-ovn#5998