nova-network associates wrong network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
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=
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-
On compute-2 I see:
/usr/sbin/dnsmasq (...) --listen-
But when I kill those dnsmasq processes and restart nova-network, then compute-2 starts dnsmasq with the configuration for compute-1.
tags: | added: network |
Changed in nova: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
I explored that this only happens if there are active VMs. It seems that the affected VMs „loose“ their compute-node association.