New issue
Advanced search Search tips

Issue 787018 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: ----



Sign in to add a comment

test_push failed: failed to load linked log

Project Member Reported by xixuan@chromium.org, Nov 20 2017

Issue description

[chromeos-staging-master2.hot.corp.google.com] out: Failed to load page for link to log: http://localhost/tko/retrieve_logs.cgi?job=/results/5085-chromeos-test/.
[chromeos-staging-master2.hot.corp.google.com] out: INFO:googleapiclient.discovery:URL being requested: POST https://www.googleapis.com/gmail/v1/users/me/messages/send?alt=json
[chromeos-staging-master2.hot.corp.google.com] out: INFO:oauth2client.client:Refreshing due to a 401 (attempt 1/2)
[chromeos-staging-master2.hot.corp.google.com] out: INFO:oauth2client.client:Refreshing access_token
[chromeos-staging-master2.hot.corp.google.com] out: DEBUG:root:Email sent: 15fda6f182966b18
[chromeos-staging-master2.hot.corp.google.com] out: Reverifying all DUTs.
[chromeos-staging-master2.hot.corp.google.com] out: INFO:oauth2client.client:Attempting refresh to obtain initial access_token
[chromeos-staging-master2.hot.corp.google.com] out: INFO:oauth2client.client:Refreshing access_token
[chromeos-staging-master2.hot.corp.google.com] out: INFO:root:Waiting for ts_mon flushing process to finish...
[chromeos-staging-master2.hot.corp.google.com] out: INFO:root:Finished waiting for ts_mon process.
[chromeos-staging-master2.hot.corp.google.com] out: Traceback (most recent call last):
[chromeos-staging-master2.hot.corp.google.com] out:   File "./site_utils/test_push.py", line 698, in <module>
[chromeos-staging-master2.hot.corp.google.com] out:     sys.exit(main())
[chromeos-staging-master2.hot.corp.google.com] out:   File "./site_utils/test_push.py", line 695, in main
[chromeos-staging-master2.hot.corp.google.com] out:     return _main(arguments)
[chromeos-staging-master2.hot.corp.google.com] out:   File "./site_utils/test_push.py", line 637, in _main
[chromeos-staging-master2.hot.corp.google.com] out:     check_queue(queue)
[chromeos-staging-master2.hot.corp.google.com] out:   File "./site_utils/test_push.py", line 527, in check_queue
[chromeos-staging-master2.hot.corp.google.com] out:     raise exc_info[0](exc_info[1])
[chromeos-staging-master2.hot.corp.google.com] out: __main__.TestPushException: Failed to load page for link to log: http://localhost/tko/retrieve_logs.cgi?job=/results/5085-chromeos-test/.
[chromeos-staging-master2.hot.corp.google.com] out:

Fatal error: run() received nonzero return code 1 while executing!

If you need to contact the on-duty trooper, see: https://chromium.googlesou
rce.com/infra/infra/+/master/doc/users/contacting_troopers.md


Missing any configs for tko redirection? Assign to last week's deputy for more info.
 
Status: xixuanchromium.org (was: Assigned)
chromeos-test@chromeos-staging-master2:~$ curl "http://localhost/tko/retrieve_logs.cgi?job=/results/5085-chromeos-test/"
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>401 Unauthorized</title>
</head><body>
<h1>Unauthorized</h1>
<p>This server could not verify that you
are authorized to access the document
requested.  Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
<hr>
<address>Apache/2.4.10 (Ubuntu) Server at localhost Port 80</address>
</body></html>

chromeos-test@chromeos-staging-master2:~$ tail -f /var/log/apache2/error.log
[Mon Nov 20 09:17:11.454682 2017] [google_sso:error] [pid 26479:tid 140480603948800] [client 127.0.0.1:36818] [gsso] Request-derived endpoint doesn't match LoginServiceNames. See go/ssoflag: "localhost" not in "chromeos-staging-master2.hot.corp.google.com"
[Mon Nov 20 09:17:11.454708 2017] [google_sso:error] [pid 26479:tid 140480603948800] [client 127.0.0.1:36818] [gsso] Request's service name invalid: localhost/
DEBUG:root:USE SHADOW RESTRICTED_GROUPS is not a valid group.
[Mon Nov 20 10:14:18.848545 2017] [google_sso:error] [pid 26479:tid 140480687875840] [client 127.0.0.1:37324] [gsso] Request-derived endpoint doesn't match LoginServiceNames. See go/ssoflag: "localhost" not in "chromeos-staging-master2.hot.corp.google.com"
[Mon Nov 20 10:14:18.848570 2017] [google_sso:error] [pid 26479:tid 140480687875840] [client 127.0.0.1:37324] [gsso] Request's service name invalid: localhost/
[Mon Nov 20 10:17:42.717846 2017] [google_sso:error] [pid 26479:tid 140480823207680] [client 127.0.0.1:37416] [gsso] Request-derived endpoint doesn't match LoginServiceNames. See go/ssoflag: "localhost" not in "chromeos-staging-master2.hot.corp.google.com"
[Mon Nov 20 10:17:42.717892 2017] [google_sso:error] [pid 26479:tid 140480823207680] [client 127.0.0.1:37416] [gsso] Request's service name invalid: localhost/
[Mon Nov 20 10:17:54.621353 2017] [mpm_event:notice] [pid 26238:tid 140480962967424] AH00491: caught SIGTERM, shutting down

....

https://g3doc.corp.google.com/company/teams/sso/howto/apache.md?cl=head#faq

It is the sso apache issue. You can work with Allen to add the missing config.
Basically adding the localhost to the LoginServiceNames, Allen did similar stuff last week

Comment 3 by xixuan@chromium.org, Nov 20 2017

Cc: -shuqianz@chromium.org
Owner: xixuan@chromium.org
Status: Assigned (was: xixuanchromium.org)
Aviv seems working on this right now, crbug.com/786106

Comment 5 by xixuan@chromium.org, Nov 20 2017

Mergedinto: 786106
Status: Duplicate (was: Assigned)
thanks! merged.

Sign in to add a comment