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/I05394e49077a72199bbc80c8cb622ec2b17f2fa7
[2]https://review.opendev.org/q/I09cc14dff6933aae63cbd43a29f9221f405ecede
[3]https://github.com/openstack/neutron/blob/e7b70521d0e230143a80974e7e4795a2acafcc9b/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#L1753
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959098
Title:
[ovn] metadata route missing on the guest
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1959098/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
