Public bug reported:
If you retrieve the schema for an image by executing this HTTP request:
GET /schemas/image
you get back this JSON schema:
{
"additionalProperties": {
"type": "string"
},
"name": "image",
"links": [
{
"href": "{self}",
Public bug reported:
Currently, the way object properties are labelled read-only is through
the description, like so:
"status": {
"enum": [
"queued",
"saving",
"active",
"killed",
"deleted",
Public bug reported:
I have the following image:
{
"status": "active",
"name": "foo",
"tags": [
"1",
"3",
"2"
],
"container_format": "ami",
"created_at": "2015-11-12T14:26:08Z",
"size": 983040,
"disk_format": "ami",
"updated_at":
Public bug reported:
According to the JSON schema spec, you can replace the entire document
using an empty string "" as the JSON pointer. If the original schema
looked like this:
{
"type": "object",
"properties": {
"foo": {"type": "string"},
"bar": {"type": "string"}
}
}
Sorry, I selected the wrong project. It should be `openstack-api-site`.
** Project changed: cinder => openstack-api-site
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Public bug reported:
When listing volume types, you get back this JSON:
{
"volume_types": [
{
"extra_specs": {
"capabilities": "gpu"
},
"id": "6685584b-1eac-4da6-b5c3-555430cf68ff",
"name": "SSD"
},
{
Public bug reported:
Request
~~~
PATCH /v3/services/42a4f85b93b5445c9c05c1482b25e5f3 HTTP/1.1
Host: {snip}:5000
X-Auth-Token: {snip}
Response
HTTP/1.1 400 Bad Request
Date: Fri, 19 Jun 2015 13:40:54 GMT
Server: Apache/2.4.7 (Ubuntu)
Vary: X-Auth-Token
x-openstack-request-id:
Public bug reported:
When I execute
GET http://xxx.xxx.xxx.xxx:35357/v3/services?page=2per_page=5
I expect to see a paginated collection returned (5 resources in total),
however this is not the case. Instead I get back the full collection -
so it seems like the query params are being ignored.
Public bug reported:
I've installed both Icehouse and Juno with devstack, and the user
operations for v2 Keystone all seem to return 404s.
- Is it possible to add/list/get/update/delete users on v2 if v3 is installed?
- If not, how do I disable v3?
** Affects: keystone
Importance:
Public bug reported:
In the docs (http://developer.openstack.org/api-ref-networking-v2.html
#quotas-ext), it clearly says that to update quota values, the request
should be:
PUT /v2.0/quotas
But I'm getting a 404 when you do this. If you do this instead:
PUT /v2.0/quotas/foo
it works as
10 matches
Mail list logo
