openstack/openstack-ansible-os_neutron
Code Issues Proposed changes

Create separate lock path for neutron-ovn-metadata-agent

Browse Source 
root user/group ownership of the neutron-ovn-metadata service caused
the neutron lock dir to be owned by root:root, which caused issues
with neutron-server's ability to write the OVN hash ring lock file
to /run/lock/neutron and prevented the creation of networks.

It appears neutron-ovn-metadata-agent needs access to the OVS DB
schema via unix:/var/run/openvswitch/db.sock, which is owned by root,
so a separate lock path has been created for the metadata agent to
workaround this.

FWIW, this issue manifested with upstream Neutron commit
536498a29a4e7662a4d0b1bb923e2521509ad77a.

Change-Id: Ib6d69bb2ce340b50140216e2abf236a1da93e46b
This commit is contained in:
James Denton 2022-12-22 05:55:48 -06:00
parent 92fa6a5295
commit d4cbd2d7ad
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
vars/main.yml
View File

@ -495,6 +495,7 @@ neutron_services:
group: neutron_ovn_controller
systemd_user_name: root
systemd_group_name: root
systemd_lock_dir: /run/lock/neutron-ovn-metadata
service_name: neutron-ovn-metadata-agent
service_en: "{{ neutron_plugin_type == 'ml2.ovn' }}"
service_conf_path: "{{ neutron_conf_version_dir }}"