Add a custom playbook to fix OVN chassis priorities #661
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
Sometimes, typically after restarting OVN services, the priorities of entries in the ha_chassis and gateway_chassis tables in the OVN northbound database can become misaligned. This results in broken routing for external (bare metal/SR-IOV) ports. This playbook can be used to fix the issue by realigning the priorities of the table entries. It does so by assigning the highest priority to the "first" (sorted alphabetically) OVN NB DB host. This results in all gateways being scheduled to a single host, but is less complicated than trying to balance them (and it's also not clear to me how to map between individual ha_chassis and gateway_chassis entries). The playbook can be run as follows: kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ovn-fix-chassis-priorities.yml If the 'controllers' group does not align with the group used to deploy the OVN NB DB, this can be overridden by passing the following: '-e ovn_nb_db_group=some_other_group'
markgoddard
force-pushed
the
wallaby-ovn-fix-chassis-priorities-playbook
branch
from
70721d5 to
3a4fa4c
Compare
cityofships
approved these changes
Sep 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes, typically after restarting OVN services, the priorities of entries in the ha_chassis and gateway_chassis tables in the OVN northbound database can become misaligned. This results in broken routing for external (bare metal/SR-IOV) ports.
This playbook can be used to fix the issue by realigning the priorities of the table entries. It does so by assigning the highest priority to the "first" (sorted alphabetically) OVN NB DB host. This results in all gateways being scheduled to a single host, but is less complicated than trying to balance them (and it's also not clear to me how to map between individual ha_chassis and gateway_chassis entries).
The playbook can be run as follows:
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ovn-fix-chassis-priorities.yml
If the 'controllers' group does not align with the group used to deploy the OVN NB DB, this can be overridden by passing the following: '-e ovn_nb_db_group=some_other_group'