yahoo-eng-team team mailing list archive

[Joshua Griffiths <jgriffiths.1993@xxxxxxxxx>]

Public bug reported:

Description
-----------
The network_data.json provided by the config drive/metadata service is missing local routes for adjacent subnets.

When using DHCP, these routes *are* provided via neutron's DHCP agent
correctly.

Steps to Reproduce
------------------
* Create a new network in Neutron with 2 subnets: 192.168.0.0/24 and 192.168.1.0/24 with gateways 192.168.0.1 and 192.168.1.1 respectively.
* Launch a new instance with an address in subnet 192.168.0.0/24 .
* Inspect the available metadata in `openstack/latest/network_data.json`

Expected Behaviour
------------------
There should be two routes specified in `network_data.json`:
* network: 0.0.0.0,     netmask: 0.0.0.0,       gateway: 192.168.0.1
* network: 192.168.1.0, netmask: 255.255.255.0, gateway: 0.0.0.0

Actual Behaviour
----------------
There is only one route specified in `network_data.json`:
* network: 0.0.0.0,     netmask: 0.0.0.0,       gateway: 192.168.0.1

Environment
-----------
* Ubuntu 14.04
* stable/newton - latest release from Git

=====

For reference to Neutron's behaviour, see: [neutron.agent.linux.dhcp]

NOTE: this is also not properly implemented in cloud-init's static
networking implementation and an issue is currently open
HERE:[https://bugs.launchpad.net/cloud-init/+bug/1663049]. This may be
relevant for anybody attempting to test the behaviour.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1663165

Title:
  network_data from metadata agent does not contain local routes for
  adjacent subnets

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  -----------
  The network_data.json provided by the config drive/metadata service is missing local routes for adjacent subnets.

  When using DHCP, these routes *are* provided via neutron's DHCP agent
  correctly.

  Steps to Reproduce
  ------------------
  * Create a new network in Neutron with 2 subnets: 192.168.0.0/24 and 192.168.1.0/24 with gateways 192.168.0.1 and 192.168.1.1 respectively.
  * Launch a new instance with an address in subnet 192.168.0.0/24 .
  * Inspect the available metadata in `openstack/latest/network_data.json`

  Expected Behaviour
  ------------------
  There should be two routes specified in `network_data.json`:
  * network: 0.0.0.0,     netmask: 0.0.0.0,       gateway: 192.168.0.1
  * network: 192.168.1.0, netmask: 255.255.255.0, gateway: 0.0.0.0

  Actual Behaviour
  ----------------
  There is only one route specified in `network_data.json`:
  * network: 0.0.0.0,     netmask: 0.0.0.0,       gateway: 192.168.0.1

  Environment
  -----------
  * Ubuntu 14.04
  * stable/newton - latest release from Git

  =====

  For reference to Neutron's behaviour, see: [neutron.agent.linux.dhcp]

  NOTE: this is also not properly implemented in cloud-init's static
  networking implementation and an issue is currently open
  HERE:[https://bugs.launchpad.net/cloud-init/+bug/1663049]. This may be
  relevant for anybody attempting to test the behaviour.

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