[SRU] With QuantumManager, nova-network does not start dnsmasq during initialization
Bug #977759 reported by
Mandar Vaze
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Mandar Vaze | ||
Essex |
Fix Released
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Chuck Short |
Bug Description
Scenario :
1. nova is configured to use QuantumManager
2. VMs are running
3. nova-network process is stopped/killed
4. All dnsmasq processes are killed
5. nova-network is restarted
Expected Result :
dnsmasq should be restarted when nova-network process comes up
Actual Result :
dnsmasq process is NOT started by nova-network during initialization
Tested On :
Branch : master
git commit nova : 384b758166ed72f
Related branches
lp://qastaging/~openstack-ubuntu-testing/nova/precise-essex-proposed
- Chuck Short: Pending requested
-
Diff: 56 lines (+14/-4)3 files modifieddebian/changelog (+8/-0)
debian/control (+6/-3)
debian/nova-console.install (+0/-1)
Changed in nova: | |
assignee: | nobody → Mandar Vaze (mandarvaze) |
tags: | added: essex-backport |
Changed in nova: | |
milestone: | none → folsom-1 |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova (Ubuntu Precise): | |
status: | New → In Progress |
Changed in nova (Ubuntu): | |
status: | New → In Progress |
Changed in nova (Ubuntu Precise): | |
milestone: | none → ubuntu-12.04.1 |
assignee: | nobody → Chuck Short (zulcss) |
tags: |
added: verification-done removed: verification-needed |
Changed in nova (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in nova: | |
milestone: | folsom-1 → 2012.2 |
To post a comment you must log in.
nova/network/ quantum/ manager. py : update_dhcp() calls restart_dhcp() which checks and starts dnsmasq if needed.
NetworkManager calls self._setup_ network_ on_host from init_host network_ on_host
For FlatDHCPManager and VlanManager update_dhcp() is called from _setup_
But QuantumManager does not call update_dhcp() during init_host() - hence the problem.