network configuration is not restored after host reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Chuck Short | ||
nova (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After rebooting a host, nova-compute fails to restart guests VM because the interface used to create vlan is not UP. In our case, this interface is not connected to a physical network and doesn't have an IP address, so it's not configured on boot.
It could be good to start nova-network even if vlan interfaces cannot be set up. Here, it crashes while trying to put a vlan interface UP, as you can see in the attached log file
For other people eventually affected by the problem, i initially wrote this script to manually configure network so nova-network can start successfully
#!/bin/sh
add_network() {
BR=br$1
VLAN=vlan$1
LAN=$2
BCAST=$3
vconfig add eth1 $1
brctl addbr $BR
brctl setfd $BR 0
brctl stp $BR off
ip link set $BR up
ip link show dev $BR
brctl addif $BR $VLAN
ip addr show dev $BR scope global
ip addr add "$LAN" brd "$BCAST" dev $BR
}
vconfig set_name_type VLAN_PLUS_
add_network 100 "172.16.0.4/24" "172.16.0.255"
add_network 101 "172.16.1.4/24" "172.16.1.255"
add_network 102 "172.16.2.4/24" "172.16.2.255"
add_network 103 "172.16.3.4/24" "172.16.3.255"
add_network 104 "172.16.4.4/24" "172.16.4.255"
Changed in nova (Ubuntu): | |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → folsom-3 |
status: | Fix Committed → Fix Released |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
Changed in nova: | |
milestone: | folsom-3 → 2012.2 |
Ok,