Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 923612

Summary: RFE: Keystone log files should reveal the source of the token
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: openstack-keystoneAssignee: Adam Young <ayoung>
Status: CLOSED NOTABUG QA Contact: Ami Jeain <ajeain>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: apevec, ayoung, dpal, jkt, nkinder, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-13 15:34:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
token logs none

Description Ofer Blaut 2013-03-20 08:08:01 UTC 
Created attachment 713099 [details]
token logs

Description of problem:

Keystone log files should reveal the source of the token (ip address).

I create a mis-configuration where i had two different setups (A & B )

by mistake i configure keystone quantum end-point in setup A to use quantum server of setup B.

in the logs files both quauntum server and keystone on setup B we could only see the messages ( as attahced ), but there was no clue about the source ip of the request, even in debug mode.

adding the identity/source ip ( in none debug mode )will help debug such issues
 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.configure quantum setup A
2.configure quantum setup B
3.configure keystone enpoint of setupB to use the quantum server of setup A
4.check keystone.log and quantum server.log on setup A

this can be tested with other services like NOVA....

configuration on setupB:

keystone service-create --name=quantum --type=network --description="Quantum Service" 

keystone endpoint-create --region RegionOne --service-id $(get_service_id quantum) --publicurl http://ip_setup_A:9696 --adminurl http://ip_setup_A:9696 --internalurl http://ip_setup_A:9696 

  
Actual results:

errors as attached no way to know about this mis-config 
Expected results:


Additional info: