OpenStack Compute (nova)

ConfigDrive uses metadata service which hits the database from within nova-compute

Bug #1120402 reported by Alessandro Pilotti on 2013-02-09

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	High	Dan Smith	OpenStack Compute (nova) 2013.1 "grizzly"

Bug Description

Booting a VM with ConfigDrive on Hyper-V fails with the following error after updating the repository:

http://paste.openstack.org/show/30885/

Dan Smith (danms) on 2013-02-09

Changed in nova:
assignee:	nobody → Dan Smith (danms)
importance:	Undecided → High
milestone:	none → grizzly-3
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-02-09: Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/21573

Dan Smith (danms) on 2013-02-09

summary:

- Cannot boot an image on Hyper-V with ConfigDrive
+ ConfigDrive uses metadata service which hits the database from within
+ nova-compute

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-02-12: Fix merged to nova (master)

Reviewed: https://review.openstack.org/21573
Committed: http://github.com/openstack/nova/commit/91db10a0fd43c30ed088082583b7d43667339ac5
Submitter: Jenkins
Branch: master

commit 91db10a0fd43c30ed088082583b7d43667339ac5
Author: Dan Smith <email address hidden>
Date: Sat Feb 9 10:32:49 2013 -0500

Make the metadata paths use conductor

This patch makes the metadata service use conductor instead of hitting the
database directly.

    It adds a get_ec2_ids() method to conductor, which encapsulates a bunch of
    very small id translation database queries. It also does the AZ lookup
    via conductor.

Fixes bug 1120402

Change-Id: Iceef753b1451ff53e29dfbf97a696b952b47d5a3