Public bug reported: curl -H 'Host: 127.0.0.1:35357' -H 'Accept-Encoding: gzip, deflate' -H 'X-Subject-Token: <TOKEN_SUBJ>' -H 'Accept: application/json' -H 'X -Auth-Token: <TOKEN_AUTH>' -H 'Connection: keep-alive' -H 'User-Agent: python-keystoneclient' http://localhost:35357/v3/auth/tokens
Keystone on behalf of the same HTTP request queries the full revocation_event table twice. SELECT revocation_event.id AS revocation_event_id, revocation_event.domain_id AS revocation_event_domain_id, revocation_event.project_id AS revocation_event_project_id, revocation_event.user_id AS revocation_event_user_id, revocation_event.role_id AS revocation_event_role_id, revocation_event.trust_id AS revocation_event_trust_id, revocation_event.consumer_id AS revocation_event_consumer_id, revocation_event.access_token_id AS revocation_event_access_token_id, revocation_event.issued_before AS revocation_event_issued_before, revocation_event.expires_at AS revocation_event_expires_at, revocation_event.revoked_at AS revocation_event_revoked_at, revocation_event.audit_id AS revocation_event_audit_id, revocation_event.audit_chain_id AS revocation_event_audit_chain_id FROM revocation_event ORDER BY revocation_event.revoked_at The full revocation_event table must not be queried multiple times on behalf of the same HTTP request, it is a waste of resources. PS.: It happens also when X-Subject-Token = X-Auth-Token. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1518902 Title: revokation list queried twice on token query Status in OpenStack Identity (keystone): New Bug description: curl -H 'Host: 127.0.0.1:35357' -H 'Accept-Encoding: gzip, deflate' -H 'X-Subject-Token: <TOKEN_SUBJ>' -H 'Accept: application/json' -H 'X -Auth-Token: <TOKEN_AUTH>' -H 'Connection: keep-alive' -H 'User-Agent: python-keystoneclient' http://localhost:35357/v3/auth/tokens Keystone on behalf of the same HTTP request queries the full revocation_event table twice. SELECT revocation_event.id AS revocation_event_id, revocation_event.domain_id AS revocation_event_domain_id, revocation_event.project_id AS revocation_event_project_id, revocation_event.user_id AS revocation_event_user_id, revocation_event.role_id AS revocation_event_role_id, revocation_event.trust_id AS revocation_event_trust_id, revocation_event.consumer_id AS revocation_event_consumer_id, revocation_event.access_token_id AS revocation_event_access_token_id, revocation_event.issued_before AS revocation_event_issued_before, revocation_event.expires_at AS revocation_event_expires_at, revocation_event.revoked_at AS revocation_event_revoked_at, revocation_event.audit_id AS revocation_event_audit_id, revocation_event.audit_chain_id AS revocation_event_audit_chain_id FROM revocation_event ORDER BY revocation_event.revoked_at The full revocation_event table must not be queried multiple times on behalf of the same HTTP request, it is a waste of resources. PS.: It happens also when X-Subject-Token = X-Auth-Token. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1518902/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp