yahoo-eng-team team mailing list archive

[Nguyen Thanh Cong <1987060@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi everybody,

I reach a bug OVN Metadata set up very slow, that make the first VM
can't get metadata.

Let's say I have network 1. In a compute that doesn't have any virtual
machines with that network, there will be no namespace ovnmeta-<network-
id> corresponding to network1.

Now I create a virtual machine with network1 in compute node, neutron-
ovn-metadata will initialize namespace ovnmeta-<network-id>. But
sometimes, I don't know why it's setup very slow, lead the VM can't get
metadata.

- The namespace has been initialized successfully
- IP address already set (IP of subnet & IP 169.254.169.254)
- Haproxy has started and is listening to port 80

*** BUT I try to login to VM and ping to namespace but it fails. And I
try ping gateway from namespace failed to.

After a while (30s or 1-2 minutes), when I can ping to gateway from
namespace or can ping metadata from VM, VM will get the metadata on
reboot.

This bug sometimes happens, not always. And usually happens on compute
node with high load (60%) and many flows (100k flows). I think it relate
to setting up slow flows.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1987060

Title:
  OVN Metadata set up very slow

Status in neutron:
  New

Bug description:
  Hi everybody,

  I reach a bug OVN Metadata set up very slow, that make the first VM
  can't get metadata.

  Let's say I have network 1. In a compute that doesn't have any virtual
  machines with that network, there will be no namespace
  ovnmeta-<network-id> corresponding to network1.

  Now I create a virtual machine with network1 in compute node, neutron-
  ovn-metadata will initialize namespace ovnmeta-<network-id>. But
  sometimes, I don't know why it's setup very slow, lead the VM can't
  get metadata.

  - The namespace has been initialized successfully
  - IP address already set (IP of subnet & IP 169.254.169.254)
  - Haproxy has started and is listening to port 80

  *** BUT I try to login to VM and ping to namespace but it fails. And I
  try ping gateway from namespace failed to.

  After a while (30s or 1-2 minutes), when I can ping to gateway from
  namespace or can ping metadata from VM, VM will get the metadata on
  reboot.

  This bug sometimes happens, not always. And usually happens on compute
  node with high load (60%) and many flows (100k flows). I think it
  relate to setting up slow flows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1987060/+subscriptions