The errors mentioned in bug description are from MetadataAgentProxy process but the one mentioned in comment#4 is from parent MetadataAgent process itself.
ovsdb.MetadataAgentOvnSbIdl().start() seems never returned and so sb_idl is not initialised [1].
However from the logs, we can see the MetadataAgent is connected to OVS DB server and the trigger of function in which error happened indicates the MetadataAgentOvnSbIdl handling OVSDB SB update events.
The errors mentioned in bug description are from MetadataAgentProxy process but the one mentioned in comment#4 is from parent MetadataAgent process itself.
ovsdb.MetadataA gentOvnSbIdl( ).start( ) seems never returned and so sb_idl is not initialised [1]. nSbIdl handling OVSDB SB update events.
However from the logs, we can see the MetadataAgent is connected to OVS DB server and the trigger of function in which error happened indicates the MetadataAgentOv
This need to looked further into IDL code.
[1] https:/ /opendev. org/openstack/ neutron/ src/commit/ 1e8197fee5031ee 7ba384eb537b13f 381a837685/ neutron/ agent/ovn/ metadata/ agent.py# L241-L248