-
Notifications
You must be signed in to change notification settings - Fork 23
fix: octavia-api broken in multinode OVS #2051
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
base: stackhpc/2025.1
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly makes the octavia_provider_drivers conditional based on whether OVN is enabled, which is a good fix for non-OVN deployments. However, the change is incomplete as it does not update the related octavia_provider_agents configuration. This will likely cause issues when OVN is disabled. I have added a comment to highlight this and suggest a fix to ensure the Octavia configuration remains consistent.
|
I don't know a correct value for the agent for amphora. |
My general strategy with things like that is to just grep through the source of kolla ansible/kayobe etc for the variable to see if I can find it defined anywhere already |
When kolla_enable_ovn is false, fallback to amphora driver
1ba4146 to
293ccdf
Compare
Thank you Alex, you are right: I should have grepped. I've corrected with |
Co-authored-by: Alex Welsh <112560678+Alex-Welsh@users.noreply.github.com>
Alex-Welsh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elelaysh does amphora actually work in a multinode? has it been tested?
|
This doc in #1362 might help |
When kolla_enable_ovn is false, fallback to amphora driver