cecdb6a175
Currently openvswitch sets system-id based on inventory_hostname, but when Ansible inventory contains ip addresses - then it will only take first ip octet - resulting in multiple OVN chassis being named i.e. "10". Then Neutron and OVN have problems functioning, because a chassis named "10" will be created and deleted multiple times per second - this ends up in ovsdb and neutron-server processes using up to 100% CPU. Adding openvswitch role to ovn CI job triggers. Change-Id: Id22eb3e74867230da02543abd93234a5fb12b31d Closes-Bug: #1884734
11 lines
502 B
YAML
11 lines
502 B
YAML
---
|
|
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.
|