QuantumManager does not correctly handle multiple nova-network nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Mandar Vaze |
Bug Description
Scenario :
========
Two hosts running nova-network process for two networks
HostA for networkA (say 10.0.8.0/24)
HostB for networkB (say 10.0.9.0/24)
Both these networks are associated with a tenant (say Demo)
Expected Result :
==============
When we launch an new VM instance, dnsmasq setup related requests from allocate_
Actual Result :
============
dnsmasq setup related request randomly goes to HostA or HostB
Additional Background :
===================
During init_host() - QuantumManager incorrectly associates self.host for all the networks, so any host associations done via "nova-manage network modify --host" are lost if one of the nova-network restarts. (In this case, both nova-networks are now "owned" by nova-network process that restarted)
So now, QuantumManager can not update dnsmasq settings correctly.
Changed in nova: | |
assignee: | nobody → Mandar Vaze (mandarvaze) |
description: | updated |
tags: | added: essex-backport |
Changed in nova: | |
importance: | Undecided → Medium |
milestone: | none → folsom-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-1 → 2012.2 |
Fix proposed to branch: master /review. openstack. org/6829
Review: https:/