VM receive no IP with FlatDHCP, if there is no network with id=1

[Mathias Nohr]

If i create a network with following command, my VMs get an IP over FlatDHCP:

nova-manage network create private --multi_host=T --fixed_range_v4=192.168.100.0/24 --num_networks=1 --bridge=br100 --bridge_interface=eth0 --network_size=255

If i delete this network and recreate it, new VM's don't get an IP.

If I change manually the network-id in the database to id=1, flatDHCP is working again.

It seems, that a network with id=1 have to be specified in the database.

I use the latest nova release from ubuntu 12.04 repositories (rc2).

My nova.conf:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--ec2_host=192.168.129.49
--rabbit_host=192.168.129.49
--nova_url=http://192.168.129.49:8774/v2/
--routing_source_ip=192.168.129.49
--glance_api_servers=192.168.129.49:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.100
--sql_connection=mysql://nova:novMYsql@192.168.129.49/nova
--ec2_url=http://192.168.129.49:8773/services/Cloud
--keystone_ec2_url=http://192.168.129.49:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
#--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://192.168.129.49:6080
--vnc_console_proxy_url=http://192.168.129.49:6080
--novncproxy_baseurl=http://192.168.129.49:6080/vnc_auto.html
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--flat_interface=eth0
--flat_network_bridge=br100
--fixed_range=192.168.100.0/24
--network_size=250
--flat_network_dhcp_start=192.168.100.2
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose

[Martin Gerhard Loschwitz (martin-loschwitz)]

I can confirm this problem with a very similar configuration and I can confirm that changing the ID of my former id=9 network to 1 fixed the problem for me.

[bhuang (bhuanggut)]

 yes,I delete this network and recreate it, new VM's don't get an IP.
Solution:
use nova;
update networks set id='1';

[John Tran (jtran)]

I'm unable to reproduce the problem.

[John Tran (jtran)]

For more detail on my attempt to reproduce the problem, I deleted the network, recreated it. Using the same nova.conf settings from above (on TRUNK and on Precise 12.04 amd64):

Verifying that the network was deleted and recreated:

$ mysql -u root -p nova -e 'select id from networks;'
Enter password:
+----+
| id |
+----+
| 2 |
+----+

Newly created instance:

$ nova list
+--------------------------------------+------+--------+----------------+
| ID | Name | Status | Networks |
+--------------------------------------+------+--------+----------------+
| d6782537-c760-4b6a-a450-25d4fcd129cb | test1 | ACTIVE | mynet=192.168.100.2 |
+--------------------------------------+------+--------+----------------+

[Vish Ishaya (vishvananda)]

This has likely been fixed by a few patches that have been backported to stable, including:

https://review.openstack.org/#/c/6174/