OVN_UUID isn't properly set in ovsdb during stack.sh

Bug #1918656 reported by Slawek Kaplonski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Fix Released
Undecided
Slawek Kaplonski

Bug Description

OVS, when is started is generating random system-id uuid and stores it in /etc/openvswitch/system-id.conf file to be reused later.
But lib/neutron_plugins/ovn_agent module in devstack got own setting OVN_UUID which can be set by user, provider in ovn-uuid file or generated randomly during stack.sh. Finally it will be set in external_ids:system-id by that module.

Problem is that later, when openvswitch service is restared, it will restore value from /etc/openvswitch/system-id.conf so OVN_UUID value isn't really effectively used at all (it's set only for about 10-20 seconds during stack.sh script).

Tags: ovn
Changed in devstack:
assignee: nobody → Slawek Kaplonski (slaweq)
Revision history for this message
Slawek Kaplonski (slaweq) wrote :
Changed in devstack:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.