Apart from what Yatin requested, that is necessary to debug this issue, can you confirm "ovn_metadata_enabled" is True? I guess it is because other subnets have this port, but doesn't harm to double check.
Just in case, please check if you have [1] and [2] in your code. If you changed the subnet parameters ("dhcp_enable") without those patches, you could be in an undefined state now.
Can you check also in the server logs, during the network creation, if the metadata port was created too? [3].
Hi Przemysław:
Apart from what Yatin requested, that is necessary to debug this issue, can you confirm "ovn_metadata_ enabled" is True? I guess it is because other subnets have this port, but doesn't harm to double check.
Just in case, please check if you have [1] and [2] in your code. If you changed the subnet parameters ("dhcp_enable") without those patches, you could be in an undefined state now.
Can you check also in the server logs, during the network creation, if the metadata port was created too? [3].
Regards.
[1]https:/ /review. opendev. org/q/I05394e49 077a72199bbc80c 8cb622ec2b17f2f a7 /review. opendev. org/q/I09cc14df f6933aae63cbd43 a29f9221f405ece de /github. com/openstack/ neutron/ blob/e7b70521d0 e230143a80974e7 e4795a2acafcc9b /neutron/ plugins/ ml2/drivers/ ovn/mech_ driver/ ovsdb/ovn_ client. py#L1753
[2]https:/
[3]https:/