neutron

OpenStack Metadata API and OVN in Neutron

Bug #1921809 reported by Arkadi Poliakevitch
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Confirmed
Low
Unassigned

Bug Description

- [x] This doc is inaccurate in this way: "Open and maintain a connection to the OVN Northbound database (using the ovsdbapp library). On first connection, and anytime a reconnect happens:

Do a full sync."

I can't see any connections from neutron_ovn_metadata_agent to OVN Northbound database and I can't find them in the python code either.

- [x] This is a doc addition request. The above means that something is missing from the documentation as when a network is created in openstack, the metadata port is not. Because the port is not created, the Port_Binding table in the OVN Southbound database is not updated and nothing happens on the chassis, i.e. the veth pair is not created, nor metadata proxy.

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

It does looks like the docs are out of date here, and I noticed they also still reference 'network:dhcp' instead of 'network:distributed' which is the device_owner for these OVN metadata ports. I'll mark as Confirmed but since the code is working will make Low priority.

Changed in neutron:
status: New → Confirmed
importance: Undecided → Low
tags: added: ovn
Revision history for this message
Arkadi Poliakevitch (arkadipol) wrote :

The code only works if the metadata port is created manually (even if owned by network:dhcp) and host route 169.254.169.254/32 via <metadata_port_ip> is setup for the subnet of the network. It took me almost two days to figure it out by studying neutron_ovn_metadata_agent python code and comparing it to the documentation.

Revision history for this message
Arkadi Poliakevitch (arkadipol) wrote :

Bizarre. Yesterday the metadata port was not created automatically but today on a fresh openstack re-install, the neutron_ovn_metadata_agent did create the metadata port automatically owned by network:distributed with the correct host routing for 169.254.169.254. Hm... but how? It does not connect to the OVN Northbound database or did I miss it?

Revision history for this message
Max Khon (fjoe) wrote (last edit ):

Do you have DHCP turned on or off in your subnet (when it did not work, and now, when it works).
See #1976366

Btw neutron-ovn-metadata-agent does not use Northbound database: it looks at Port_Binding table in Southbound database instead.

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

Other bug subscribers

Remote bug watches

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