neutron-linuxbridge-cleanup.service uses wrong config file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
High
|
Corey Bryant | ||
Mitaka |
Fix Released
|
High
|
Corey Bryant | ||
neutron (Ubuntu) |
Fix Released
|
High
|
Corey Bryant | ||
Xenial |
Fix Released
|
High
|
Corey Bryant |
Bug Description
1)
Version information:
neutron-
Installed: 2:8.1.2-0ubuntu1
Candidate: 2:8.1.2-0ubuntu1
Version table:
*** 2:8.1.2-0ubuntu1 500
500 http://
500 http://
500 http://
500 http://
100 /var/lib/
2:
500 http://
500 http://
500 http://
500 http://
2)
lsb:
Description: Ubuntu 16.04 LTS
Release: 16.04
3)
The service should start successful with the correct and sane configuration.
4)
It fails to start as it uses the wrong config (/etc/neutron/
It should use:
/etc/neutron/
This should happen like for neutron-
For this service it is specified in:
/etc/init.
A similar file exists for cleanup:
/etc/init.
Changed in neutron (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in cloud-archive: | |
status: | Triaged → Fix Released |
Changed in neutron (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
Hi Paul,
Thanks for reporting this bug. This looks to be a valid bug and I'll work on a fix for this. Adding some triage below for now.
Looking at an install of the neutron- linuxbridge- agent package, /etc/neutron/ plugins/ ml2/linuxbridge _agent. ini includes the following section:
[linux_bridge]
# ml2.linuxbridge .agent
# From neutron.
#
# Comma-separated list of <physical_ network> :<physical_ interface> tuples interface_ mappings =
# mapping physical network names to the agent's node-specific physical network
# interfaces to be used for flat and VLAN networks. All physical networks
# listed in network_vlan_ranges on the server should have mappings to
# appropriate interfaces on each agent. (list value)
#physical_
# List of <physical_ network> :<physical_ bridge> (list value)
#bridge_mappings =
And the linuxbridge cleanup code does indeed access options such as physical_ interface_ mappings and bridge_mappings:
https:/ /github. com/openstack/ neutron/ blob/master/ neutron/ cmd/linuxbridge _cleanup. py#L31 /github. com/openstack/ neutron/ blob/master/ neutron/ cmd/linuxbridge _cleanup. py#L39
https:/