Ambiguous neutron-ovn setup docs

Bug #2017674 reported by
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Following up on this thread [1], the neutron-ovn setup is confusing. Looking in the "networking-ovn/latest" doc some of the necessary steps are to configure the core_plugin and service_plugin like this:

core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin
service_plugins = networking_ovn.l3.l3_ovn.OVNL3RouterPlugin

This seems to fail when starting neutron-server. In the manual neutron installation guide to set up neutron-ovn [2] the config is slightly different:

core_plugin = ml2
service_plugins = ovn-router

According to the OP the latter config options seem to work. This should be merged to have unambiguous documentation steps across the different pages.


This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [X] This doc is inaccurate in this way: There different doc versions for the same setup, one of them doesn't work.
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - Ask OpenStack:
 - The mailing list:
 - IRC: 'openstack' channel on Freenode

Release: on 2019-01-23 11:29:27
SHA: eda5d7f80d877601170631c5f5485370ea701f42

Revision history for this message
Brian Haley (brian-haley) wrote :

The networking-ovn repository has been retired and all code moved to the neutron repository a number of cycles ago. For that reason you should only be using the guide(s) referenced there, for example your [2] link.

If you find any issues there please re-open this bug.

Changed in networking-ovn:
status: New → Invalid
Revision history for this message (eblock) wrote :

Thanks for the quick response. How do you determine that is retired? The only noticeable thing on that page for me is the last update of that page from 2019, but that may not be the first thing a user is looking for. Shouldn't there be some info box or a flag or anything pointing out that the content is not relevant anymore?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.