Image registration (ec2) is broken using deprecated auth
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Undecided
|
Unassigned | ||
Essex |
Fix Released
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
It seems image registration via ec2 no longer functions when using deprecated auth. Reproducible using Essex or deploying devstack, changing it to use deprecated auth (in both nova and glance), creating project/
ubuntu@
ubuntu@
Tue Apr 10 06:49:01 UTC 2012: using testbucket/
[image ] testimg.img => testbucket/
Tue Apr 10 06:49:01 UTC 2012: checking for existing registered image at testbucket/
Tue Apr 10 06:49:02 UTC 2012: bundling image testimg.img
Tue Apr 10 06:49:03 UTC 2012: upload testbucket/
Tue Apr 10 06:49:03 UTC 2012: register testbucket/
Tue Apr 10 06:49:04 UTC 2012: registered at testbucket/
Tue Apr 10 06:49:04 UTC 2012: ami-0000000a testbucket/
ami-0000000a testbucket/
ubuntu@
ImageNotFound: Image ami-0000000a could not be found.
In nova-api.log, after the intial upload appears to have completed,:
2012-04-10 06:49:04 INFO nova.api.ec2 [req-0ee2216b-
Traceback (most recent call last):
File "/usr/lib/
readers.
File "/opt/stack/
self.
File "/opt/stack/
self.
File "/opt/stack/
raise exception.
ImageNotFound: Image c4e23453-
Removing descriptor: 7
The exception is coming from nova.image.
{'container_
'disk_format': 'ami',
'is_public': False,
'name': u'testbucket/
'properties': {'architecture': 'x86_64',
'status': 'queued'}
Adding this information into the metadata for the deprecated_auth case as follows http://
Related branches
- 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 (Ubuntu): | |
importance: | Undecided → High |
tags: | added: ubuntu-openstack-upgrade |
Changed in nova: | |
status: | New → Won't Fix |
Adam, glance. py (from the trace) and api/ec2/cloud.py (from your patch, nothing jumped out at me).
Thanks, I'm wondering what regressed this. just looking at git logs on nova/image/s3.py nova/image/