similar to https://bugs.launchpad.net/glance/+bug/1447322
please refer glance meeting [1] for reason behind marking this as invalid
[1]
http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-19-14.01.log.html
** Changed in: glance
Status: In Progress => Invalid
--
You
Talking with a couple of developers, it appears the upstream docs will
be updated as well as the code, changing this to response code to a 409
** Changed in: glance
Status: Invalid = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Ankit is totally right that 403 is a valid response here. The rfc2616
defines 403 as The server understood the request, but is refusing to
fulfill it which is exactly what is happening in this scenario.
The API docs haven't been updated yet [1], as image deactivation is
fresh feature. There is an
3 matches
Mail list logo
