Looks like you are using Ussuri.
In case of OVN the route is not supposed to be used:
https://docs.openstack.org/networking-
ovn/latest/contributor/design/metadata_api.html
Instead OVN does all the proxying in OVN layer (see above)
--
You received this bug notification because you are a member
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: neutron (Ubuntu)
Status: New => Confirmed
--
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:
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
Hi Przemysław Lal,
What you mean by "affected" network? Do you mean there are multiple
networks in your setup, and out of those only one such network is
misbehaving in terms of routes?
If above is true, is the "affected" network misbehaving since when it's
created, or it used to work earlier and
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
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
10 matches
Mail list logo
