yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #08012
[Bug 1266926] [NEW] log files should reveal source of the request
Public bug reported:
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:
Origianlly reported:
https://bugzilla.redhat.com/show_bug.cgi?id=923612
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1266926
Title:
log files should reveal source of the request
Status in OpenStack Identity (Keystone):
New
Bug description:
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:
Origianlly reported:
https://bugzilla.redhat.com/show_bug.cgi?id=923612
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1266926/+subscriptions
Follow ups
References