Could you check what version of keystoneclient you're using? If it's <0.2 I would suggest updating and seeing if that makes the logging go away. Previously there was a place where there was an expected EndpointNotFound (when receiving an unscoped token) which was being logged as an exception despite being perfectly acceptable. This was fixed and subsequently released in the latest keystoneclient.
Could you check what version of keystoneclient you're using? If it's <0.2 I would suggest updating and seeing if that makes the logging go away. Previously there was a place where there was an expected EndpointNotFound (when receiving an unscoped token) which was being logged as an exception despite being perfectly acceptable. This was fixed and subsequently released in the latest keystoneclient.