Add endpoint template failed with 400 Expecting endpoint template

Bug #888170 reported by Jenny Vo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Medium
Yogeshwar

Bug Description

Add Endpoint template call failed with '400 Expecting Endpoint template'
here example raw request:
POST http://localhost:35357/v2.0/OS-KSCATALOG/endpointTemplates HTTP/1.1

Accept-Encoding: gzip,deflate

X-Auth-Token: 999888777666

Accept: application/xml

Content-Type: application/xml;charset=UTF-8

User-Agent: Jakarta Commons-HttpClient/3.1

Host: localhost:35357

Content-Length: 533

<v1:endpointTemplate adminURL="http://127.0.0.1:35357/v2.0" enabled="true" global="true" id="1" internalURL="http://127.0.0.1:5000/v2.0" name="Compute" publicURL="http://keystone.publicinternets.com/v2.0" region="South" type="compute" xmlns:v1="http://docs.openstack.org/identity/api/ext/OS-KSCATALOG/v1.0"><v1:version id="1" info="https://compute.north.public.com/v1/ " list="https://compute.north.public.com/"/><atom:link href="https://service-href.com" rel="author" xmlns:atom="http://www.w3.org/2005/Atom"/></v1:endpointTemplate>

Revision history for this message
Yogeshwar (yogesh-srikrishnan) wrote :
Changed in keystone:
status: New → Confirmed
assignee: nobody → Yogeshwar (yogesh-srikrishnan)
importance: Undecided → Medium
Revision history for this message
Jeff Highley (jeff-highley) wrote : Re: Auth LB change Nov 15
Download full text (18.2 KiB)

Tom,

We are seeing the 405 error when we go directly against Cloud Auth – now that the LB rule has been removed. Is this a problem that you guys are looking into?

Thanks,

Jeff

From: Nicholas Mistry <<email address hidden><mailto:<email address hidden>>>
Date: Wed, 9 Nov 2011 13:56:56 -0600
To: Jeff Highley <<email address hidden><mailto:<email address hidden>>>
Cc: Tom Hopkins <<email address hidden><mailto:<email address hidden>>>, Antony Messerli <<email address hidden><mailto:<email address hidden>>>, Ziad Sawalha <<email address hidden><mailto:<email address hidden>>>
Subject: Re: Auth LB change Nov 15

Correction. *content not contact.
--
Nicholas N. Mistry
work: 210.312.4806 mobile:210.452.5630

From: Nicholas Mistry <<email address hidden><mailto:<email address hidden>>>
Date: Wed, 9 Nov 2011 13:38:31 -0600
To: Jeff Highley <<email address hidden><mailto:<email address hidden>>>
Cc: Tom Hopkins <<email address hidden><mailto:<email address hidden>>>, Antony Messerli <<email address hidden><mailto:<email address hidden>>>, Tom Hopkins <<email address hidden><mailto:<email address hidden>>>, Ziad Sawalha <<email address hidden><mailto:<email address hidden>>>
Subject: Re: Auth LB change Nov 15

Jeff,
In the email I sent to Tom, I included requests for both the original endpoint and the redirect. This "testing" is actually just a preliminary verification step, just to be sure we are getting back valid contact before trying the nova-client stuff.

Copying the content here for your review:

Alex,

I am trying to verify the JSON fixes in the auth2.0 staging environment, before trying novaclient. Seems like something has changed and im now getting a 301 redirect and a 405 back. Can you take a look into this?

Thanks

-N

MFV25BDF91:novatest nich3909$ curl -X POST https://auth.staging.us.ccp.rackspace.net/v2.0/tokens -d '{"auth":{"tenantName": "5801124", "passwordCredentials":{"username":"cp24c","password":"Jtester1"}}}' -H "Content-type: application/json" --verbose --insecure
* About to connect() to auth.staging.us.ccp.rackspace.net port 443 (#0)
* Trying 10.13.75.159... connected
* successfully set certificate verify locations:
* CAfile: /opt/local/share/curl/curl-ca-bundle.crt
  CApath: none
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using RC4-SHA
* Server certificate:
* subject: C=US; ST=Texas; O=Rackspace; OU=Chris Maier; CN=auth.staging.us.ccp.rackspace.net
* start date: 2011-09-15 19:18:47 GMT
* expire date: 2021-09-12 19:18:47 GMT
* common name: auth.staging.us.ccp.rackspace.net (matched)
* issuer: C=US; ST=Texas; L=San Antonio; O=Rackspace; OU=System Administration; CN=Rackspace Internal Root CA; <email address hidden><mailto:<email address hidden>>
* SS...

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to keystone (master)

Reviewed: https://review.openstack.org/1461
Committed: http://github.com/openstack/keystone/commit/fb98f6bfcb18b2531167c82f6c3df82327249b96
Submitter: Jenkins
Branch: master

 status fixcommitted
 done

commit fb98f6bfcb18b2531167c82f6c3df82327249b96
Author: Yogeshwar Srikrishnan <email address hidden>
Date: Wed Nov 9 11:35:59 2011 -0600

    Bug 888170: Fixing references to incorrect schema.

    Change-Id: I738d8c45078a17481856a3b2661fa9436d86df78

Changed in keystone:
status: Confirmed → Fix Committed
Changed in keystone:
milestone: none → essex-2
Thierry Carrez (ttx)
Changed in keystone:
status: Fix Committed → Fix Released
Revision history for this message
Jenny Vo (jenny-vo) wrote :

Test - Fixed

Thierry Carrez (ttx)
Changed in keystone:
milestone: essex-2 → 2012.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.