If any of the subnets of a network have DHCP capabilities, the metadata port of this network namespace will have no IP assigned (exactly the OVN metadata code you are pointing [1]). That means we can't provide the metadata via the metadata IP. You need to use a config-drive in this case [2].
Hello Max:
If any of the subnets of a network have DHCP capabilities, the metadata port of this network namespace will have no IP assigned (exactly the OVN metadata code you are pointing [1]). That means we can't provide the metadata via the metadata IP. You need to use a config-drive in this case [2].
Regards.
[1]https:/ /github. com/openstack/ neutron/ blob/09207ba731 bfc859c2f6d1755 88a8bfe09be01db /neutron/ agent/ovn/ metadata/ agent.py# L431-L437 /docs.openstack .org/nova/ latest/ admin/config- drive.html
[2]https:/