yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1949097@xxxxxxxxxxxxxxxxxx>]

Hello:

Routes are pushed by DHCP server.

I'll mark this bug as invalid as this is not a problem in the OVS
metadata service or OVN DHCP service.

Regards.

** Changed in: neutron
       Status: New => Invalid

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

Title:
  Cloud-Init cannot contact Meta-Data-Service on Xena with OVN

Status in neutron:
  Invalid

Bug description:
  ## Brief
  When running Xena with OVN, neither debian nor cirros cloud-init bootstraps can reach the meta-data service during boot.

  - Using Wallaby+OVN works.
  - Using Xena+OVS works.

  Assuming this must be a regression in Xena, when OVN is used

  ## Pre-Conditions:
  - Xena
  - OVN
  - Cirros Cloud init boot

  Other environment details:
  - non DVR - (not sure it is required, but that is what has been used)
  - Debian 11 hosts (if that is a required, but that is what has been used)
  - Ubuntu based docker - images (if that is a required, but that is what has been used)

  Reproduction:
  You can use https://github.com/EugenMayer/openstack-lab/tree/stable/ovn and run 'make start' to setup a vagrant setup. Vanilla-Kolla is used to deploy, based on the kolla 'stable/xena' branches.

  After the deployment the following API request should be run:
  https://github.com/EugenMayer/openstack-
  lab/blob/stable/ovn/README.setup.md

  The booted cirros instance should already show the errors.

  The exact same stack can be tested using wallaby here
  https://github.com/EugenMayer/openstack-lab/blob/stable/ovn-wallaby -
  it will work. The only things that have been changed is the inventory
  and ansible: https://github.com/EugenMayer/openstack-
  lab/compare/stable/ovn...stable/ovn-wallaby?expand=1

  ## Expected output:
  The cirros instance can reach the meta-data service like that (boot logs)

  --------
  WARN: failed: route add -net "0.0.0.0/0" gw "10.10.0.1"
  OK
  checking http://169.254.169.254/2009-04-04/instance-id
  successful after 1/20 tries: up 9.89. iid=i-00000002
  failed to get http://169.254.169.254/2009-04-04/user-data
  warning: no ec2 metadata for user-data
  --------

  ## Actual Output
  --------
  route: SIOCADDRT: File exists
  WARN: failed: route add -net "0.0.0.0/0" gw "10.10.0.1"
  OK
  checking http://169.254.169.254/2009-04-04/instance-id
  failed 1/20: up 1.34. request failed
  failed 2/20: up 50.36. request failed
  failed 3/20: up 99.38. request failed
  --------

  ## Version

  Yet hard to understand for me, since those are not tagged yet.
  What-ever https://github.com/openstack/kolla-ansible/tree/stable/xena deploys

  ## Severity

  Blocks us from using Xena entirely

  ## More Informations

  Interface TCPDUMP and namespace information:
  https://gist.github.com/EugenMayer/3b7d1fc4a42d7fc911229f38eec891dd

  In the meta-data agent, i can see this configuration.
  On the compute instance, i see those 2 running https://gist.github.com/EugenMayer/b6611b9725a7697d0a392c1b3c1a5683

  Those are the debug logs https://gist.github.com/EugenMayer/e2c5796f7c547c224a3aaccad2c35257
  Normal logs: https://gist.github.com/EugenMayer/bbda954d207fc03b1fd9ea0bb6d143cf

  https://gist.github.com/EugenMayer/fda894a3c6bb2bde5b9d1756b234cd79

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