← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1347318] [NEW] tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON.test_rescope_token race fails with DB2

 

Public bug reported:

This is against master level (juno) code with DB2 10.5, sqlalchemy-
migrate 0.9.1 and sqlalchemy 0.8.4 on RHEL 6.5, seeing race fails with
the
tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON.test_rescope_token
(and xml) tests like this:

Traceback (most recent call last):\n  File
"/tmp/tempest/tempest/tempest/api/identity/admin/v3/test_tokens.py",
line 145, in test_rescope_token\n    domain=\'Default\')\n  File
"/tmp/tempest/tempest/tempest/services/identity/v3/json/identity_client.py",
line 579, in auth\n    resp, body = self.post(self.auth_url,
body=body)\n  File "/tmp/tempest/tempest/tempest/common/rest_client.py",
line 218, in post\n    return self.request(\'POST\', url, extra_headers,
headers, body)\n  File
"/tmp/tempest/tempest/tempest/services/identity/v3/json/identity_client.py",
line 605, in request\n    \'Unexpected status code
{0}\'.format(resp.status))\nIdentityError: Got identity error\nDetails:
Unexpected status code 404

The test is fine with MySQL, it looks like an issue with the expired_at
timestamp:

A breakpoint in keystone/contrib/revoke/model.py, is_revoked():

mysql:

(Pdb) p self.revoke_map
{'trust_id=*': {'consumer_id=*': {'access_token_id=*': {'expires_at=2014-07-22 22:55:53': {'domain_id=*': {'project_id=*': {u'user_id=949c28307de74cafb4ab07c6ada75d6c': {'role_id=*': {'issued_before': datetime.datetime(2014, 7, 22, 21, 55, 59, 610579)}}}}}}}}}

DB2:

(Pdb) p self.revoke_map
{'trust_id=*': {'consumer_id=*': {'access_token_id=*': {'expires_at=2014-07-22 22:58:44.322976': {'domain_id=*': {'project_id=*': {u'user_id=c4ed3fa9ee5f4e02b580389400a817e0': {'role_id=*': {'issued_before': datetime.datetime(2014, 7, 22, 21, 58, 49, 390556)}}}}}}}}}

** Affects: keystone
     Importance: Undecided
         Status: New


** Tags: db2

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

Title:
  tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON.test_rescope_token
  race fails with DB2

Status in OpenStack Identity (Keystone):
  New

Bug description:
  This is against master level (juno) code with DB2 10.5, sqlalchemy-
  migrate 0.9.1 and sqlalchemy 0.8.4 on RHEL 6.5, seeing race fails with
  the
  tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON.test_rescope_token
  (and xml) tests like this:

  Traceback (most recent call last):\n  File
  "/tmp/tempest/tempest/tempest/api/identity/admin/v3/test_tokens.py",
  line 145, in test_rescope_token\n    domain=\'Default\')\n  File
  "/tmp/tempest/tempest/tempest/services/identity/v3/json/identity_client.py",
  line 579, in auth\n    resp, body = self.post(self.auth_url,
  body=body)\n  File
  "/tmp/tempest/tempest/tempest/common/rest_client.py", line 218, in
  post\n    return self.request(\'POST\', url, extra_headers, headers,
  body)\n  File
  "/tmp/tempest/tempest/tempest/services/identity/v3/json/identity_client.py",
  line 605, in request\n    \'Unexpected status code
  {0}\'.format(resp.status))\nIdentityError: Got identity
  error\nDetails: Unexpected status code 404

  The test is fine with MySQL, it looks like an issue with the
  expired_at timestamp:

  A breakpoint in keystone/contrib/revoke/model.py, is_revoked():

  mysql:

  (Pdb) p self.revoke_map
  {'trust_id=*': {'consumer_id=*': {'access_token_id=*': {'expires_at=2014-07-22 22:55:53': {'domain_id=*': {'project_id=*': {u'user_id=949c28307de74cafb4ab07c6ada75d6c': {'role_id=*': {'issued_before': datetime.datetime(2014, 7, 22, 21, 55, 59, 610579)}}}}}}}}}

  DB2:

  (Pdb) p self.revoke_map
  {'trust_id=*': {'consumer_id=*': {'access_token_id=*': {'expires_at=2014-07-22 22:58:44.322976': {'domain_id=*': {'project_id=*': {u'user_id=c4ed3fa9ee5f4e02b580389400a817e0': {'role_id=*': {'issued_before': datetime.datetime(2014, 7, 22, 21, 58, 49, 390556)}}}}}}}}}

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


Follow ups

References