Actually I can confirm ovn_metadata_enabled is set to "True". I was
looking in the wrong place (compute/metadata agent server) and this
seems to be set in the API server node:
/etc/neutron# grep -r ovn_metadata
plugins/ml2/ml2_conf.ini:ovn_metadata_enabled = True
ovn.ini:#ovn_metadata_enabled =
affected network/subnet information
** Attachment added: "LP1959098-affected-network.txt"
https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/5588891/+files/LP1959098-affected-network.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
unaffected network/subnet information
** Attachment added: "LP1959098-unaffected-network.txt"
https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/5588890/+files/LP1959098-unaffected-network.txt
** Attachment removed: "LP1959098-affected-network.txt"
** Attachment added: "LP1959098-affected-network.txt"
https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/559/+files/LP1959098-affected-network.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We hit this issue today as well. Same symptoms:
* Failed to get metadata during VM launch - consistently and only on the
"affected" network. Other networks like "unaffected" are OK.
* Missing metadata route inside VM
* After adding the route manually to the .2 IP we can ping/curl the metadata
