yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #31126
[Bug 1441075] [NEW] Unable to update image location using v2 api.
Public bug reported:
I am using vanilla glance with commit-id
6dc5477a12b9b904332ac6fe7932abbc7a0275a7
Operations I did using glance client library and results of those operations:
glance.images.create(name='i2') -->passed successfully
glance.images.update('827f09fe-6173-4ab8-9331-4aba0333654e', location='abc', disk_format='qcow2', container_format='bare') --> Didn't pass
--------------
Response:
---------------
HTTPForbidden: <html>
<head>
<title>403 Forbidden</title>
</head>
<body>
<h1>403 Forbidden</h1>
Attribute 'location' is reserved.<br /><br />
</body>
</html> (HTTP 403)
The strange thing is that I can use a glance client which uses v1 api and do the operation and it passes.
g1.images.update('827f09fe-6173-4ab8-9331-4aba0333654e', location='http://google.com', disk_format='qcow2', container_format='bare')
The same issue occurs while using glance cli as well. Even the help
options in glance cli does not show --location while using v2 api.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1441075
Title:
Unable to update image location using v2 api.
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
I am using vanilla glance with commit-id
6dc5477a12b9b904332ac6fe7932abbc7a0275a7
Operations I did using glance client library and results of those operations:
glance.images.create(name='i2') -->passed successfully
glance.images.update('827f09fe-6173-4ab8-9331-4aba0333654e', location='abc', disk_format='qcow2', container_format='bare') --> Didn't pass
--------------
Response:
---------------
HTTPForbidden: <html>
<head>
<title>403 Forbidden</title>
</head>
<body>
<h1>403 Forbidden</h1>
Attribute 'location' is reserved.<br /><br />
</body>
</html> (HTTP 403)
The strange thing is that I can use a glance client which uses v1 api and do the operation and it passes.
g1.images.update('827f09fe-6173-4ab8-9331-4aba0333654e', location='http://google.com', disk_format='qcow2', container_format='bare')
The same issue occurs while using glance cli as well. Even the help
options in glance cli does not show --location while using v2 api.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1441075/+subscriptions
Follow ups
References
