upgrading neutron appended faulty core_plugin option in neutron.conf
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Upgrading our neutron packages to Ocata, the following:
Using xenial ocata cloudarchive repo:
deb http://
ii neutron-common 2:10.0.
ii neutron-dhcp-agent 2:10.0.
ii neutron-l3-agent 2:10.0.
ii neutron-
ii neutron-
ii neutron-plugin-ml2 2:10.0.
ii neutron-server 2:10.0.
ii python-neutron 2:10.0.
ii python-
ii python-neutron-lib 1.1.0-0ubuntu1~
ii python-
What happend was that "core_plugin = openvswitch" was appended to neutron.conf even though we have core_plugin = ml2 set.
Removed that line, restarted the agent and everything was fine again.
| description: | updated |
| description: | updated |
| James Page (james-page) wrote | #1 |
| Changed in neutron (Ubuntu): | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in neutron (Ubuntu): | |
| status: | Incomplete → Expired |
I'm not sure where "core_plugin = openvswitch" is coming from; the packaging sets the core_plugin to ml2 using a patch to the generated neutron.conf file (using oslo-config-
The way that the files in /etc/neutron are handled by the packaging means they are treated as dpkg conf files - in the case that something has been changed post install, and upgrade should by default not write a new version of the configuration file to disk.