IptablesFirewallDriver prevents instance to get IP address from DHCP server in case of nova installation on multiple machines
Bug #707554 reported by
Tushar Patil
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Critical
|
Tushar Patil | ||
Bug Description
Tested on Revision no: 606
I have installed nova on 2 machines
1) network, scheduler, api and objectstore services running on one machine
2) compute and volume service running on another.
Flags
--network_
If I run a new instance, the instance doesn't get the ip address from the DHCP server (dnsmasq).
Seems like there is some issue in the iptablesfirewal
Related branches
lp:~tpatil/nova/bug707554
- Vish Ishaya (community): Approve
- Devin Carlen (community): Approve
- Tushar Patil: Pending requested
-
Diff: 33 lines (+5/-4)2 files modifiedAuthors (+1/-0)
nova/virt/libvirt_conn.py (+4/-4)
Revision history for this message
| Tushar Patil (tpatil) wrote | #1 |
Revision history for this message
| Vish Ishaya (vishvananda) wrote | #2 |
| Changed in nova: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
Revision history for this message
| Tushar Patil (tpatil) wrote | #3 |
| Changed in nova: | |
| assignee: | nobody → Tushar Patil (tpatil) |
| Changed in nova: | |
| assignee: | Tushar Patil (tpatil) → NTT DATA (nttdata) |
| Changed in nova: | |
| assignee: | NTT DATA (nttdata) → Tushar Patil (tpatil) |
| Changed in nova: | |
| status: | Confirmed → In Progress |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → 2011.1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Let's get this merged. Tushar, are you going to make a branch for this and propose?