yahoo-eng-team team mailing list archive

[Evgeny Antyshev <eantyshev@xxxxxxxxx>]

Public bug reported:

We run tempest in such an environment that all ssh keys, personality files, etc. go through metadata service.
Which requires metadata route to 169.254.169.254 being provided by DHCP.

We faced rather complicated problem in scenario/test_network_v6.py:

Networking configuration comprises of 4 steps:
1) Private network creation
2) Router creation and plugging it as a gateway in external network
3) Subnet creation
4) Adding router interface to the subnet

This sequence leads to that DHCP service provides static metadata route, and our scenario works.
That's how it is done in create_networks() from tempest/scenario/manager.py (which used in the majority of tests).

But, prepare_network() of scenario/test_network_v6.py first creates subnet, and after that it creates router (1-3-2-4).
DHCP service configuration in neutron regards this subnet isolated then (which is what I don't understand), therefore,
doesn't provide it with metadata route by default (force_metadata=False, enable_isolated_metadata=False).

It really seems like Neutron has a bug handling such scenario: it
doesn't update DHCP service configuration when router is created for
subnet.

Also, AFAIU, all the upstream Jenkins dsvm tempest jobs running test_dualnet* get metadata from config drive,
 that's possibly why they aren't affected.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: tempest

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

Title:
  [tempest] No metadata route in test_dualnet* family

Status in neutron:
  New

Bug description:
  We run tempest in such an environment that all ssh keys, personality files, etc. go through metadata service.
  Which requires metadata route to 169.254.169.254 being provided by DHCP.

  We faced rather complicated problem in scenario/test_network_v6.py:

  Networking configuration comprises of 4 steps:
  1) Private network creation
  2) Router creation and plugging it as a gateway in external network
  3) Subnet creation
  4) Adding router interface to the subnet

  This sequence leads to that DHCP service provides static metadata route, and our scenario works.
  That's how it is done in create_networks() from tempest/scenario/manager.py (which used in the majority of tests).

  But, prepare_network() of scenario/test_network_v6.py first creates subnet, and after that it creates router (1-3-2-4).
  DHCP service configuration in neutron regards this subnet isolated then (which is what I don't understand), therefore,
  doesn't provide it with metadata route by default (force_metadata=False, enable_isolated_metadata=False).

  It really seems like Neutron has a bug handling such scenario: it
  doesn't update DHCP service configuration when router is created for
  subnet.

  Also, AFAIU, all the upstream Jenkins dsvm tempest jobs running test_dualnet* get metadata from config drive,
   that's possibly why they aren't affected.

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