New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
roachtest: prefix all logs with worker tags #114045
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
E-quick-win
Likely to be a quick win for someone experienced.
T-testeng
TestEng Team
Projects
Comments
RaduBerinde
added
the
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
label
Nov 8, 2023
cc @cockroachdb/test-eng |
srosenberg
added
the
E-quick-win
Likely to be a quick win for someone experienced.
label
Nov 16, 2023
exalate-issue-sync
bot
removed
the
E-quick-win
Likely to be a quick win for someone experienced.
label
Nov 16, 2023
srosenberg
added
the
E-quick-win
Likely to be a quick win for someone experienced.
label
Nov 20, 2023
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 13, 2024
Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by wX tags to see what each worker is doing. This PR prefixes the worker tags to logs that were missing them. Epic: none Fixes: cockroachdb#114045 Release note: None
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 13, 2024
Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by wX tags to see what each worker is doing. This PR prefixes the worker tags to logs that were missing them. Epic: none Fixes: cockroachdb#114045 Release note: None
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 14, 2024
Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by wX tags to see what each worker is doing. This PR prefixes the worker tags to logs that were missing them. Epic: none Fixes: cockroachdb#114045 Release note: None
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 14, 2024
Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by wX tags to see what each worker is doing. This PR prefixes the worker tags to logs that were missing them. Epic: none Fixes: cockroachdb#114045 Release note: None
craig bot
pushed a commit
that referenced
this issue
May 14, 2024
123697: ccl,sql,util: Fix jwt auth and add sensitive error logs r=souravcrl a=souravcrl ccl,sql,util: Fix jwt auth and add sensitive error logs We are running into issues with jwt authentication and currently unable to provide support as we are not logging the error from the http client used in the authenticator. The PR looks to propagate this obtained error from `ValidateJWTLogin` http client. The http client now also respects the system http proxy if set. Validated the error details when presenting an expired token ``` ERROR: JWT authentication: invalid token SQLSTATE: 28000 DETAIL: unable to parse token: exp not satisfied Failed running "sql" ``` Validated error on setting wrong proxy params ``` ERROR: JWT authentication: unable to validate token SQLSTATE: 28000 Failed running "sql" ``` and logged error: ``` I240510 08:31:28.604141 1473 4@util/log/event_log.go:32 ⋮ [T1,Vsystem,n1,client=127.0.0.1:56289,hostssl,user=‹sourav.sarangi›] 3 ={"Timestamp":1715329888604122000,"EventType":"client_authentication_failed","InstanceID":1,"Network":"tcp","RemoteAddress":"‹127.0.0.1:56289›","SessionID":"17ce136f2a8ecd480000000000000001","Transport":"hostssl","User":"‹sourav.sarangi›","SystemIdentity":"‹sourav.sarangi›","Reason":"CREDENTIALS_INVALID","Detail":"JWT authentication: unable to validate token\nunable to fetch jwks: Get \"https://accounts.google.com/.well-known/openid-configuration\": proxyconnect tcp: dial tcp [::1]:3129: connect: connection refused","Method":"jwt_token"} ``` Verified access logs after setting up squid proxy and passing env HTTP_PROXY and HTTPS_PROXY params ``` 1715103871.761 144 ::1 TCP_TUNNEL/200 5708 CONNECT accounts.google.com:443 - HIER_DIRECT/74.125.200.84 - 1715103871.836 73 ::1 TCP_TUNNEL/200 5964 CONNECT www.googleapis.com:443 - HIER_DIRECT/142.250.182.10 - ``` fixes #123575, CRDB-38386, CRDB-38408 Epic None Release note: Noneccl,sql,util: Fix jwt auth and add sensitive error logs We are running into issues with jwt authentication and currently unable to provide support as we are not logging the error from the http client used in the authenticator. The PR looks to propagate this obtained error from `ValidateJWTLogin` http client. The http client now also respects the system http proxy if set. Validated the error details when presenting an expired token ``` ERROR: JWT authentication: invalid token SQLSTATE: 28000 DETAIL: unable to parse token: exp not satisfied Failed running "sql" ``` Validated error on setting wrong proxy params ``` ERROR: JWT authentication: unable to validate token SQLSTATE: 28000 Failed running "sql" ``` and logged error: ``` I240510 08:31:28.604141 1473 4@util/log/event_log.go:32 ⋮ [T1,Vsystem,n1,client=127.0.0.1:56289,hostssl,user=‹sourav.sarangi›] 3 ={"Timestamp":1715329888604122000,"EventType":"client_authentication_failed","InstanceID":1,"Network":"tcp","RemoteAddress":"‹127.0.0.1:56289›","SessionID":"17ce136f2a8ecd480000000000000001","Transport":"hostssl","User":"‹sourav.sarangi›","SystemIdentity":"‹sourav.sarangi›","Reason":"CREDENTIALS_INVALID","Detail":"JWT authentication: unable to validate token\nunable to fetch jwks: Get \"https://accounts.google.com/.well-known/openid-configuration\": proxyconnect tcp: dial tcp [::1]:3129: connect: connection refused","Method":"jwt_token"} ``` Verified access logs after setting up squid proxy and passing env HTTP_PROXY and HTTPS_PROXY params ``` 1715103871.761 144 ::1 TCP_TUNNEL/200 5708 CONNECT accounts.google.com:443 - HIER_DIRECT/74.125.200.84 - 1715103871.836 73 ::1 TCP_TUNNEL/200 5964 CONNECT www.googleapis.com:443 - HIER_DIRECT/142.250.182.10 - ``` fixes #123575, CRDB-38386, CRDB-38408 Epic None Release note: None 124027: roachtest: prefix all logs with worker tags r=vidit-bhat a=vidit-bhat Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by `wX` tags to see what each worker was doing. This PR prefixes worker tags to the logs that were missing them. Epic: none Fixes: #114045 Release note: None Co-authored-by: Sourav Sarangi <sourav.sarangi@cockroachlabs.com> Co-authored-by: Vidit Bhat <vidit.bhat@cockroachlabs.com>
craig bot
pushed a commit
that referenced
this issue
May 14, 2024
124027: roachtest: prefix all logs with worker tags r=vidit-bhat a=vidit-bhat Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by `wX` tags to see what each worker was doing. This PR prefixes worker tags to the logs that were missing them. Epic: none Fixes: #114045 Release note: None Co-authored-by: Vidit Bhat <vidit.bhat@cockroachlabs.com>
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 14, 2024
Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by wX tags to see what each worker is doing. This PR prefixes the worker tags to logs that were missing them. Epic: none Fixes: cockroachdb#114045 Release note: None
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 14, 2024
Previously, many of the runner logs didn't have the worker tags. This was inadequate because we couldn't break up the logs by wX tags to see what each worker is doing. This PR prefixes the worker tags to logs that were missing them. Epic: none Fixes: cockroachdb#114045 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
E-quick-win
Likely to be a quick win for someone experienced.
T-testeng
TestEng Team
Many of the runner logs don't have the worker tag (see below). It would be ideal if all messages had it and you could in principle break up the logs by
wX
tags to see what each worker is doing.Jira issue: CRDB-33316
The text was updated successfully, but these errors were encountered: