d4cbd2d7ad
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 |
||
|---|---|---|
| .. | ||
| debian.yml | ||
| distro_install.yml | ||
| main.yml | ||
| redhat.yml | ||
| source_install.yml | ||