metadata service reports to support 1.0 but serves incorrect data
Bug #942868 reported by
Ante Karamatić
This bug report is a duplicate of:
Bug #948595: Default api-paste.ini does not properly route metadata requests to /1.0.
Edit
Remove
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Triaged
|
Medium
|
Unassigned | ||
| pyjuju |
Confirmed
|
High
|
Unassigned | ||
Bug Description
When getting machine-id from metadata service:
# curl http://
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
output is incorrect. What should happen (I guess) is:
# curl http://
i-00000001
as show by:
# curl http://
i-00000001
| Changed in juju: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Patrick Hetu (patrick-hetu) wrote | #1 |
Revision history for this message
| Roman Yepishev (rye) wrote | #2 |
| tags: | added: canonistack |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: low-hanging-fruit |
| tags: | added: ec2 |
To post a comment you must log in.
I think you have the route instruction missing in the "[composite:
[composite:
use = egg:Paste#urlmap
/: metaversions
/latest: meta
/1.0: meta <----------------
/2007-01-19: meta
/2007-03-01: meta
/2007-08-29: meta
/2007-10-10: meta
/2007-12-15: meta
/2008-02-01: meta
/2008-09-01: meta
/2009-04-04: meta