ec2 metadata block device mapping duplicate entry

Bug #1224412 reported by John Garbutt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

The ec2 metadata now seems to have both an ami and root disk entry.

It seems like the work to add the root disk into the block device mapping the the database has caused this duplicate entry.

Tags: api
Revision history for this message
John Garbutt (johngarbutt) wrote :

For example, when launching cirros I guest:

"block-device-mapping": {"ami": "xvda", "root": "/dev/xvda"}

Changed in nova:
assignee: nobody → Mike BRIGHT (k5-openstack)
Revision history for this message
Craig Tracey (craigtracey) wrote :

Hey John,

I have launched EBS-backed instances in EC2 and they have both "root" and "ami." The only discrepancy here is that on EC2 they both use the device path (in my case '/dev/sda1').

How are you querying this data, and are you perhaps comparing different API versions?

Craig

Changed in nova:
assignee: Mike BRIGHT (k5-openstack) → nobody
Changed in nova:
status: New → Incomplete
summary: - e2c metadata block device mapping duplicate entry
+ ec2 metadata block device mapping duplicate entry
Revision history for this message
Sean Dague (sdague) wrote :

old bug

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.