Comment 6 for bug 1928031

Revision history for this message
Hemanth Nakkina (hemanth-n) wrote :

After looking into errors in case description and logs in comment #4, both seems to fail waiting for sb_idl object.

AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl'
AttributeError: 'MetadataAgent' object has no attribute 'sb_idl'

Once the failure is in MetadataAgent process and the other time in forked MetadataAgentProxy process.

There is no TimeOut exception second time as this patch is applied [1] which retries the connections without timeout. However in both the cases we can see logs like below which says SSL connection to OVSDB DB is successful.
INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:10.216.241.118:6642: connected

Seems to stuck at wait_for_change [2]

On neutron-server side, these scenario's are handled by retry logic on getting IDL objects and waiting for post-fork events, see [3], [4]
Similar logic is required for neutron-ovn-metadata-agent as well. I wil submit a patch shortly for review.

[1] https://review.opendev.org/c/openstack/neutron/+/788596
[2] https://opendev.org/openstack/neutron/src/commit/87f7abb86cad13c8bc04b4e6165600ee6fd9ef7c/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/impl_idl_ovn.py#L53-L56
[3] https://opendev.org/openstack/neutron/src/commit/87f7abb86cad13c8bc04b4e6165600ee6fd9ef7c/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/impl_idl_ovn.py#L222-L226
[4] https://review.opendev.org/c/openstack/neutron/+/781555