← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1490690] [NEW] Discovery fails for V3 when admin not exposed

 

Public bug reported:

V3 is not specifically rtied to either public or Admin in the specs, but
practically speaking, it is  tied to admin;

When attempting to use the V3 api and the admin port is not exposed, the
followng happens:

$ echo $OS_AUTH_URL 
https://hostname/v3

$ openstack server list
ERROR: openstack Unable to establish connection to https://hostname:35357/v3/auth/tokens


Running on debug shows more information:
RESP BODY: {"version": {"status": "stable", "updated": "2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}, {"base": "application/xml", "type": "application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": [{"href": "https://keystone-admin.dream.io:35357/v3/";, "rel": "self"}]}}


It is the link in that response being used for discovery.  That should be the public URL, not the admin.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1490690

Title:
  Discovery fails for V3 when admin not exposed

Status in Keystone:
  New

Bug description:
  V3 is not specifically rtied to either public or Admin in the specs,
  but practically speaking, it is  tied to admin;

  When attempting to use the V3 api and the admin port is not exposed,
  the followng happens:

  $ echo $OS_AUTH_URL 
  https://hostname/v3

  $ openstack server list
  ERROR: openstack Unable to establish connection to https://hostname:35357/v3/auth/tokens

  
  Running on debug shows more information:
  RESP BODY: {"version": {"status": "stable", "updated": "2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}, {"base": "application/xml", "type": "application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": [{"href": "https://keystone-admin.dream.io:35357/v3/";, "rel": "self"}]}}

  
  It is the link in that response being used for discovery.  That should be the public URL, not the admin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1490690/+subscriptions