vlan100 and br100 still available after stopping nova-network: restart of nova-network not possible, br100 in state DOWN after starting nova-network
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Vish Ishaya | ||
Bug Description
After starting nova-network I have two new interfaces:
---snip---
6: vlan100@eth0: <BROADCAST,
link/ether 00:14:5e:6d:66:20 brd ff:ff:ff:ff:ff:ff
inet6 fe80::214:
valid_lft forever preferred_lft forever
7: br100: <BROADCAST,
link/ether 00:14:5e:6d:66:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/25 brd 192.168.0.127 scope global br100
---snap---
First problem: br100 is in state DOWN. I think this should be up..?
After stopping nova-network the two interfaces are still available:
---snip---
6: vlan100@eth0: <BROADCAST,
link/ether 00:14:5e:6d:66:20 brd ff:ff:ff:ff:ff:ff
inet6 fe80::214:
valid_lft forever preferred_lft forever
7: br100: <BROADCAST,
link/ether 00:14:5e:6d:66:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/25 brd 192.168.0.127 scope global br100
---snap---
If I now try to start nova-network again I become an error, because now we're using "ip address add" to assign the ip adress and not ifconfig (ifconfig overwrites the old settings) --> failed because the ip address is already there from the last time.
I think first of all br100 has to be set into state UP after starting nova-network. Second all vlan-interfaces and all bridges has to be stopped and to be removed after stopping nova-network. Then there is no problem while adding the new ip address after starting nova-network.
Is that right in this way..? I think that's an urgent problem and we should commit a fix asap.
---snip---
Feb 8 15:26:41 mandarin 2011-02-08 15:26:41,592 CRITICAL nova.root [-] Unexpected error while running command. Command: sudo ip addr add 192.168.
---snap---
/etc/nova.
[...]
--network_
--fixed_
--network_size=5000
Related branches
- Vish Ishaya (community): Disapprove
- Devin Carlen (community): Approve
-
Diff: 16 lines (+3/-3)1 file modifiednova/network/linux_net.py (+3/-3)
- Devin Carlen (community): Approve
- Jay Pipes (community): Approve
- Thierry Carrez (community): Abstain
-
Diff: 95 lines (+57/-11)1 file modifiednova/network/linux_net.py (+57/-11)
| summary: |
- vlan100 and br100 still available after stopping nova-network + vlan100 and br100 still available after stopping nova-network: restart + of nova-network not possible, br100 in state DOWN after starting nova- + network |
| Christian Berendt (berendt) wrote | #1 |
| Christian Berendt (berendt) wrote | #2 |
| Vish Ishaya (vishvananda) wrote | #3 |
| Changed in nova: | |
| importance: | Undecided → High |
| status: | New → In Progress |
| assignee: | nobody → Vish Ishaya (vishvananda) |
| Vish Ishaya (vishvananda) wrote | #4 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → 2011.2 |
| status: | Fix Committed → Fix Released |
br100 is not set up because of a wrong intent in method ensure_bridge(). I'll link my branch later...
--- nova/network/
+++ nova/network/
@@ -203,9 +203,9 @@
- _execute("sudo ip link set %s up" % bridge)
- else:
- _execute("sudo ip link set %s up" % bridge)
+
+ _execute("sudo ip link set %s up" % bridge)
+
if FLAGS.use_
(out, err) = _execute("sudo iptables -N nova_forward",