nova-compute cannot brctl addif br100 to the correct interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya |
Bug Description
When the machine that runs nova-compute has a different network interface (e.g. eth2) from the machine that runs nova-network (e.g. eth1), nova-compute binds br100 to the same interface as nova-network.
To illustrate, I present my own setup.
Node-1 is the control node. Installed all the nova packages except nova-compute.
--flat_
--flat_
Node-2 is the compute nodes, only the nova-compute is installed.
--flat_
--flat_
The correct setup is that br100 binds to eth1 on Node-1, and on Node-2 br100 binds to eth4.
In fact, however, nova.compute.
I solved this problem by binding br100 to eth4 in /etc/network/
Anyone who has different network interface names on two machines can re-produce this problem.
Is this a real bug, or did I miss something in the config?
2012-03-02 21:16:11 DEBUG nova.compute.
2012-03-02 21:16:11 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap brctl addif br100 eth1 from (pid=28281) execute /usr/lib/
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
the patch for bug 833426 fixed this for vlan mode, but we never put in a fix for flat network mode.