Glance v1 API makes requests to the v2 registry
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Dharini Chandrasekar |
Bug Description
If I configure storage quotas with:
user_storage_quota = 6
And I enable the v2 registry:
data_api = glance.
Then a v1 image create:
$ glance --os-image-
413 Request Entity Too Large: Denying attempt to upload image because it exceeds the quota: The size of the data 145 will exceed the limit. -5794 bytes remaining. (HTTP 413)
Generates the following request to the v2 registry:
POST /rpc HTTP/1.1.
Host: 0.0.0.0:9191.
Accept-Encoding: identity.
Content-Length: 151.
x-auth-token: bee70651417c474
.
[{"command": "user_get_
Amusingly, this works.
But I'm pretty sure it's not what we intended.
Changed in glance: | |
assignee: | nobody → wangxiyuan (wangxiyuan) |
Changed in glance: | |
assignee: | wangxiyuan (wangxiyuan) → nobody |
Changed in glance: | |
assignee: | nobody → Dharini Chandrasekar (dharini-chandrasekar) |
Changed in glance: | |
importance: | Undecided → Medium |
tags: | added: ocata-rc-potential |
Changed in glance: | |
milestone: | none → pike-1 |
I tested it in my env. When use glance. db.registry. api in glance-api.conf, api will sent a rpc message to registry. Then registry use db.sqlalchemy.api to get the data from db.
So, Stuart, what the problem? Could you describe more detail?