Hi everyone,
We are using OVN together with Openstack(Ussuri) with one of the late master
versions of ovn (83296a42e) and we see the following issue. After booting a VM
it is not possible to reach the metadata service in the corresponding network
namespace of the neutron-ovn-metadata-agent.service.
It also turned out that a recompute of the rules on the ovn-controller fixes
the issue. After more debugging we could identify the change that introduced
this situation:
commit d4bca93c0851c2f0b739411cd49ce32e3b8263bb "controller: Don't allocate
zone ids for non-VIF port bindings."
diff --git a/controller/ovn-controller.c b/controller/ovn-controller.c
index 678419ab3..739048cf8 100644
--- a/controller/ovn-controller.c
+++ b/controller/ovn-controller.c
@@ -1919,6 +1919,11 @@ ct_zones_runtime_data_handler(struct engine_node *node,
void *data)
struct shash_node *shash_node;
SHASH_FOR_EACH (shash_node, &tdp->lports) {
struct tracked_lport *t_lport = shash_node->data;
+if (strcmp(t_lport->pb->type, "")) {
+/* We allocate zone-id's only to VIF lports. */
+continue;
+}
+
if (t_lport->tracked_type == TRACKED_RESOURCE_NEW) {
if (!simap_contains(&ct_zones_data->current,
t_lport->pb->logical_port)) {
Anyone has an idea how to fix it?
Regards,
Benjamin
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
