ovn-controller: No bridge for localnet port is not an error

Bug #1865127 reported by Frode Nordahl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ovn (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Example log messages:
bridge not found for localnet port 'provnet-9d4a9910-01c3-4fe3-bae3-0d93dc6c9b69' with network name 'physnet1'

Filing here for tracking and for pointing anybody hitting it to the patch.

There is a pattern among CMSes to create a `localnet` port
binding without any chassis affiliation.

It is then up to the user to configure chassis with external
connectivity by adding a mapping under the
`external_ids:ovn-bridge-mappings` key in the Open_vSwitch
table of the local OVS instance. This may be some chassis
or all chassis depending on end user requirements.

At present `ovn-controller` will repeatedly log an error on
chassis without mapping for a localnet port while in reality
it is not an error.

A fix for this was proposed but was NACK'ed:
https://patchwork.ozlabs.org/patch/1245848/

After re-evaluation a different version of essentially the same patch was accepted upstream:
https://patchwork.ozlabs<email address hidden>/

James Page (james-page)
Changed in ovn (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Frode Nordahl (fnordahl)
description: updated
Revision history for this message
Frode Nordahl (fnordahl) wrote :

The fix is in 20.06 in Groovy

Changed in ovn (Ubuntu):
status: Triaged → Fix Committed
Frode Nordahl (fnordahl)
Changed in ovn (Ubuntu):
status: Fix Committed → Fix Released
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.