openstack/kolla-ansible
Code Issues Proposed changes

Merge "openvswitch: Use ansible_hostname for system-id"

Browse Source
This commit is contained in:
Zuul 2020-06-26 08:46:14 +00:00 committed by Gerrit Code Review
commit 6f26907a0a
3 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ansible/roles/openvswitch/defaults/main.yml
View File

@ -75,4 +75,4 @@ openvswitch_vswitchd_extra_volumes: "{{ openvswitch_extra_volumes }}"
# OpenvSwitch
#############
openvswitch_system_id: "{{ inventory_hostname_short }}"
openvswitch_system_id: "{{ ansible_hostname }}"

10
releasenotes/notes/bug-1884734-ec054799d3300778.yaml Normal file
View File

@ -0,0 +1,10 @@
---
fixes:
- |
Fixes an issue when using ip addresses instead of hostnames in Ansible
inventory. OpenvSwitch role sets system-id based on inventory_hostname,
which in case of ip addresses in is first ip octet.
Such a deployment would result in multiple OVN chassis with duplicate name
e.g. "10" connecting to OVN Southbound database - which spawns high numbers
of create/delete events in Encap database table - leading to near 100% CPU
usage of OVN/OVS/Neutron processes.

2
zuul.d/base.yaml
View File

@ -168,7 +168,7 @@
parent: kolla-ansible-base
voting: false
files:
- ^ansible/roles/(ovn|neutron)/
- ^ansible/roles/(neutron|openvswitch|ovn)/
- ^tests/test-ovn.sh
- ^tests/test-core-openstack.sh
vars: