yahoo-eng-team team mailing list archive

[Bob Ball <1220621@xxxxxxxxxxxxxxxxxx>]

wishlist for nova network; we're now focused on Neutron.

** Changed in: nova
   Importance: Low => Wishlist

** Changed in: nova
       Status: Confirmed => Won't Fix

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

Title:
  xenapi: network bridge not created on hypervisor

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  In a multi-host environment (using FlatDHCP):

  $ cat /etc/nova/nova.conf | grep DH
  network_manager = nova.network.manager.FlatDHCPManager

  Create a new network (bridge does not exist!)
  /usr/local/bin/nova-manage --config-file /etc/nova/nova.conf network create private 192.168.99.1/24 1 256 --bridge cuccos124

  And boot an instance
  nova boot --image fbc1f160-ed57-4553-908b-c16e66c7735b --flavor 1 --nic net-id=7ea39722-f66a-4b5b-bfc6-5b1b7680d2e4 blahblah

  Traceback (most recent call last):
    File "/opt/stack/nova/nova/compute/manager.py", line 1014, in _build_instance
      set_access_ip=set_access_ip)
    File "/opt/stack/nova/nova/compute/manager.py", line 1302, in _spawn
      LOG.exception(_('Instance failed to spawn'), instance=instance)
    File "/opt/stack/nova/nova/compute/manager.py", line 1298, in _spawn
      block_device_info)
    File "/opt/stack/nova/nova/virt/xenapi/driver.py", line 180, in spawn
      admin_password, network_info, block_device_info)
    File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 514, in spawn
      undo_mgr.rollback_and_reraise(msg=msg, instance=instance)
    File "/opt/stack/nova/nova/utils.py", line 981, in rollback_and_reraise
      self._rollback()
    File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 502, in spawn
      setup_network_step(undo_mgr, vm_ref, vdis)
    File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 153, in inner
      rv = f(*args, **kwargs)
    File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 449, in setup_network_step
      rescue)
    File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 537, in _setup_vm_networking
      self._create_vifs(vm_ref, instance, network_info)
    File "/opt/stack/nova/nova/virt/xenapi/vmops.py", line 1593, in _create_vifs
      vm_ref=vm_ref, device=device)
    File "/opt/stack/nova/nova/virt/xenapi/vif.py", line 55, in plug
      self._session, vif['network']['bridge'])
    File "/opt/stack/nova/nova/virt/xenapi/network_utils.py", line 51, in find_network_with_bridge
      raise Exception(_('Found no network for bridge %s') % bridge)
  Exception: Found no network for bridge cuccos124

  In domU, the bridge is created:
  $ ifconfig cuccos124
  cuccos124 Link encap:Ethernet  HWaddr 12:fa:73:38:0b:93  
            inet addr:192.168.99.3  Bcast:192.168.99.255  Mask:255.255.255.0
            inet6 addr: fe80::10fa:73ff:fe38:b93/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
            RX bytes:0 (0.0 B)  TX bytes:938 (938.0 B)

  I would expect the bridge being created on XenServer as well.

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