I've seen similar odd behavior when using the Keystone client to try to
list endpoints created using the v3 API (via puppet). Try using the
openstack client  and the v3 endpoint. Be sure to set --os-api-version 3.
On Feb 2, 2016 3:06 AM, "Pradip Mukhopadhyay" <pradip.inte...@gmail.com>
wrote:

> Hello,
>
>
> I did a stacking recently, noticing a behavior:
>
> eystone --os-username admin --os-password secretadmin --os-tenant-name
> admin --os-auth-url http://host:5000/v2.0 endpoint-list
>
> Returns null URLs for public/internal/admin.
>
>
>
> +----------------------------------+-----------+-----------+-------------+----------+----------------------------------+
> |                id                |   region  | publicurl | internalurl |
> adminurl |            service_id            |
>
> +----------------------------------+-----------+-----------+-------------+----------+----------------------------------+
> | 169f7f5090ea442c8ae534d6cd38c484 | RegionOne |           |
> |          | 8d30999ba36943359b4e7c4ae4f0a15c |
> | 255f7316074d4aecb34b69e3f28309c1 | RegionOne |           |
> |          | f26931e1fa43438da4c32fe530f33796 |
>
>
> Some of the keystone CLIs are not working. e.g. user-list is working. But
> not the others, say service-list/role-list. It is returning : The resource
> could not be found. (HTTP 404) (Request-ID:
> req-b52eace0-b65a-4ba3-afb9-616689a0833e)
>
>
> Not sure what I have messed up.
>
>
> Any help would be solicited.
>
>
>
>
> --pradip
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to