Repository navigation
Create an external router when testing L3RouterScheduling - #3833
Merged
Merged
Conversation
github-actions
Bot
added
edit:networking
|
Coverage is 63.54% — winiciusallan:fix-l3-scheduling-test into gophercloud:main. No base build found for |
Contributor
|
Nice one, LGTM, took a quick look at when the tests failed it was due to ML2/OVN now exposing the L3 agent scheduler API https://opendev.org/openstack/neutron/commit/fd27815e2e |
dlaw4608
approved these changes
Jul 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
The ML2/OVN plugin provides information about the agent binding from the chassis binding. If we don't create an external router, the logical router port would not exist and thus not binding to any host.
Fixes #3817