Linux Bridge Container Permission Issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Description
===========
When deploying TripleO using Linux Bridge (instead of Open vSwitch), the Neutron service is ran on bare-metal as the "neutron" user. This causes conflicts with data being read and written to /var/lib/
Steps to reproduce
==================
Deploy TripleO with the template `environments/
Expected result
===============
Neutron resources work with proper routing.
Actual result
=============
The linuxbridge-agent service does not work.
Environment
===========
I was testing with Queens and I assume this probably affects newer versions of TripleO, too.
Logs & Configs
==============
Error from /var/log/
Workaround: http://
The workaround does not automagically fix any existing/broken resources created while the permissions were incorrect.
There is also a note in the environment Heat template stating how it is not containerized: https:/
Changed in tripleo: | |
status: | Confirmed → Triaged |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
This only affects older versions of TripleO. CentOS 8 (used by >= Train) does not ship bridge-utils which includes the `brctl` utility required. Using Linux Bridge will no longer be supported (it never was officially supported anyways).