yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
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/1211784

Title:
  nova-network associates wrong network

Status in OpenStack Compute (nova):
  Expired

Bug description:
  OpenStack Grizzly on Ubuntu 12.04, Multi host setup.

  I'm creating 3 different networks:

  # nova-manage network create --label compute-1 --fixed_range_v4 192.168.1.0/27 --num_networks 1 --network_size 32
  # nova-manage network create --label compute-2 --fixed_range_v4 192.168.2.0/27 --num_networks 1 --network_size 32
  # nova-manage network create --label compute-3 --fixed_range_v4 192.168.3.0/27 --num_networks 1 --network_size 32

  Not every compute node may use every network because they are
  distributed over different data centers. So I need to associate the
  hosts to the networks:

  # nova-manage network modify --host=compute-1 192.168.1.0/27
  # nova-manage network modify --host=compute-2 192.168.2.0/27
  # nova-manage network modify --host=compute-3 192.168.3.0/27

  1. Issue

  Now, when I call the following command:

    `nova boot --image <uuid> --flavor m1.medium --availability-zone eu-
  central-1 test`

  The created VM gets 3 NICs due to the multinic feature. But in fact,
  only one network is suitable because the other 2 networks aren't even
  associated with the hosts.

  Workaround:

  I need to specify the host and the network.

    `nova boot --image --nic net-id=<uuid-of-net-on-compute-1> <uuid>
  --flavor m1.medium --availability-zone eu-central-1:compute-1 test`

  Unfortunately this bypasses some useful scheduling balancer
  algorithms.

  2. Issue

  After creating the networks, I can see appropriate dnsmasq processes.
  On compute-1 I see:

  /usr/sbin/dnsmasq (...) -listen-address=192.168.1.1 --except-
  interface=lo --dhcp-
  range=set:compute-1,192.168.1.1,static,255.255.255.224,120s (...)

  On compute-2 I see:

  /usr/sbin/dnsmasq (...) --listen-address=192.168.2.1 --except-
  interface=lo --dhcp-
  range=set:compute-2,192.168.2.1,static,255.255.255.224,120s (...)

  But when I kill those dnsmasq processes and restart nova-network, then
  compute-2 starts dnsmasq with the configuration for compute-1.

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