Public bug reported:
The API doesn't return all public and private flavors by default.
Effectively only public flavors are listed even though the default policy rule
authorize it.
Here I'm using 'admin' user/project along with no explicit policy
therefore relying on the default 'built-in'
@jichenjc,
You're right the behaviour is as expected, because with current devstack
the service endpoint for nova comes up with
http://192.168.1.8/compute/v2.1 which obviously points directly to a
version.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification
Public bug reported:
Whether there is only one or multiple version available, the dict key is
expected to be "versions" per the version discovery guidelines [1].
$ curl -i -H "X-Auth-Token: $OS_TOKEN" http://192.168.1.8/compute/v2.1/
HTTP/1.1 200 OK
Public bug reported:
The API reference http://developer.openstack.org/api-
ref/networking/v2/index.html doesn't reflect the fact a Qos Policy
linked to an existing network can be updated:
$ curl -s -H "X-Auth-Token: $OS_TOKEN" http://${OS_HOST}:9696/v2.0/qos/policies
| python -mjson.tool{
Public bug reported:
When authenticated via admin token, trusts details are not available.
Trusts can be listed:
---
# openstack trust list -f csv
ID,Expires At,Impersonation,Project ID,Trustee User ID,Trustor User
ID
Public bug reported:
A name field in Keystone DB is needed for helping identifying trusts.
Effectively , there could be multiple trusts for a same
project/trustor/trustee including the same expiry date and same
impersonate flag. And the same combination could have multiple trusts
assigned with
Public bug reported:
# openstack --version
openstack 1.5.0
The roles field has an extra blank character:
openstack trust show -f shell bba74b46c9744efeb1b6ce3bac6b0d40
deleted_at=None
expires_at=None
id=bba74b46c9744efeb1b6ce3bac6b0d40
impersonation=False
Public bug reported:
Using keystone V3 trusts (Kilo 2015.1.0)
Deleting a non expired trust works as expected, meanwhile when trying to
remove an expired trust, Keystone returns the trust doesn't exist.
Also nothing in the documentation [1] indicates expired trusts cannot be
removed or have to
Public bug reported:
Creating Keystone V3 trusts (Kilo 2015.1.0) with python-openstackclient
(OSC) 1.5.0 works fine when using trustor user and trustee user names
but doesn't when using IDs.
Keystone log (verbose) doesn't return any error/warning, so that might
be an OSC issue.
# openstack user
9 matches
Mail list logo
