2011-05-31 13:57:41 DEBUG [glance.registry] 1 custom properties...
2011-05-31 13:57:41 DEBUG [glance.registry] type: ramdisk
2011-05-31 13:57:41 DEBUG [glance.api.v1.images] Uploading image data for image 4 to s3 store
2011-05-31 13:57:41 ERROR [glance.api.v1.images] Error uploading image: body_file_seekable
What I'm doing for this test case is putting my S3 credentials into /etc/glance/glance-api.conf, starting glance and then running the following command:
root@glance1:~# glance add name="ari-tty" type="ramdisk" disk_format="ari" container_format="ari" is_public=true < /tmp/tty_linux/ramdisk
Failed to add image. Got error:
400 Bad Request
The server could not comply with the request since it is either malformed or otherwise incorrect.
Error uploading image: body_file_seekable
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.
Hey Jay,
I just tried this and I'm still getting:
2011-05-31 13:57:41 DEBUG [glance.registry] 1 custom properties... api.v1. images] Uploading image data for image 4 to s3 store api.v1. images] Error uploading image: body_file_seekable
2011-05-31 13:57:41 DEBUG [glance.registry] type: ramdisk
2011-05-31 13:57:41 DEBUG [glance.
2011-05-31 13:57:41 ERROR [glance.
What I'm doing for this test case is putting my S3 credentials into /etc/glance/ glance- api.conf, starting glance and then running the following command:
root@glance1:~# glance add name="ari-tty" type="ramdisk" disk_format="ari" container_ format= "ari" is_public=true < /tmp/tty_ linux/ramdisk
Failed to add image. Got error:
400 Bad Request
The server could not comply with the request since it is either malformed or otherwise incorrect.
Error uploading image: body_file_seekable
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.
---
Am I doing something wrong here?