can't run cros tryjob with a patch on internal gerrit |
||||||
Issue descriptionI am trying to start a tryjob involving an internal gerrit patch: cros tryjob -g '*563062' --hwtest reef-paladin-tryjob and get this error message: 18:18:43: WARNING: A transient error occured while querying chrome-internal-review.googlesource.com: GET /a/changes/563062/detail?o=CURRENT_REVISION&o=CURRENT_COMMIT HTTP/1.1 HTTP/1.1 403 Forbidden Response body: '<!DOCTYPE html><html lang=en><meta charset=utf-8><meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"><title>Error 403 (Forbidden)!!1</title><style>*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{color:#222;text-align:unset;margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px;}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}pre{white-space:pre-wrap;}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}</style><div id="af-error-container"><a href=//www.google.com><span id=logo aria-label=Google></span></a><p><b>403.</b> <ins>That\xe2\x80\x99s an error.</ins><p>You do not have access to this page.<br/>\n\n\nInvalid authentication credentials.\n\nPlease generate a new identifier:\n https://chrome-internal-review.googlesource.com/new-password\n\n\n<br/><a href="https://accounts.google.com/ServiceLogin?service=gerritcodereview&continue=https://chrome-internal-review.googlesource.com/login/?continue%3Da/changes/563062/detail" style="color: #777">Sign in</a><br/><br/> <ins>That\xe2\x80\x99s all we know.</ins></div>' X-ErrorId: 403, EFERW-189,EFERW-152,GSHT-204,AF-312,AF-138,AF-128,GFF-171,STSFSPSF-194,GFFFCW-294,GFFFCW-294,GFFFCW-294,GFFFCW-294,GFFFCW-294,STSFSPSF-194,GFFGAF-247,AF-124,MFMF-130,ATF-56,MFMF-130,CAF-131,MFMF-130,MFMF-133,MFMF-133,MFMF-133,MFMF-133,SCZFI-174,MFMF-130,SCMDRF-185,MFMF-130,EF-123,MFMF-130,MFMF-133,MFMF-133,MFMF-133,MFMF-133,MFMF-133,MF-34,GUUAF-142,GBLHCF-116,TF-46,TF-46,GCHSRF-63,STSF-153,PLRHF-269,TTLF-155,IIIHF-47,EUCDLF-106,GSI-95,RR-116 18:18:43: WARNING: conn.sock.getpeername(): ('2607:f8b0:400e:c06::52', 443, 0, 0) which boils down to vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv You do not have access to this page. Invalid authentication credentials. Please generate a new identifier: https://chrome-internal-review.googlesource.com/new-password ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ which I do, it results in an update to ~/.gitcookies, but the error persists when I try running the tryjob again.
,
Feb 7 2018
I can run that tryjob command without error. That means it's not a general system failure. clean$cros tryjob -g '*563062' --hwtest reef-paladin-tryjob Verifying patches... Submitting tryjob... Successfully sent PUT request to [buildbucket_bucket:master.chromiumos.tryserver] with [config:reef-paladin-tryjob] [buildbucket_id:8955217830468461072]. Tryjob submitted! To view your tryjobs, visit: http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8955217830468461072 https://uberchromegw.corp.google.com/i/chromiumos.tryserver/waterfall?committer=dgarrett@google.com&builder=paladin
,
Feb 7 2018
When you click on "chrome-internal-review.googlesource.com" does the little icon at the top right show your google account, or chromium account?
,
Feb 7 2018
Also, did this used to work and just stop? If so, have you updated to glinux, or otherwise wiped your home directory/credentials in the mean time?
,
Feb 7 2018
,
Feb 7 2018
Re: #3 my account on chrome-internal-review is @google.com Re: #4 - I have not done this in a long time, and I don't even recall if I ever ran a tryjob for an internal patch.
,
Feb 7 2018
any more suggestions, Don?
,
Feb 7 2018
My only thought is to rename your .gitcookies and .gitconfig, then try again to redo the auth from scratch. If that doesn't work, maybe there is a problem with your Gerrit permissions? If we want a Gerrit admin to investigate, just set the owner to empty. That'll put this in their triage queue.
,
Feb 7 2018
btw, does the fact that 'repo upload' for internal gerrit works fine give any extra clues? gerrit -g chrome-internal mine fails both inside and outside of chroot. Also, is your account on the internal gerrit @google or @chromium?
,
Feb 8 2018
this is stil broken for me, I can't test patches required for making progress on reef and bob devices...
,
Feb 8 2018
If the CL is viewable in a browser, then Gerrit permissions are fine. Please confirm: 1) There's NO ~/.netrc file. 2) ~/.gitcookies has a line similar to: chrome-internal-review.googlesource.com,FALSE,/,TRUE,2147483647,o,git-vbendeb.google.com=1/gK... (Important parts here is '-review' and google.com). 3) ~/.gitcookie does NOT have a line similar to: .googlesource.com,TRUE,/,TRUE,2147483647,o,.... (If it exists, it may override google.com cookie above). --- If 'repo upload' works, but 'cros tryjob' doesn't means later is parsing credentials in some different way. Either way I'm pretty sure it is not Gerrit permission issues, and thus Infra>Git>Admin queue is wrong queue...
,
Feb 8 2018
but there is .netrc file, used for authentication with other services. It had lines for GOB instances, once I removed the lines the problem went away. Thank you! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by xixuan@chromium.org
, Feb 7 2018Owner: dgarr...@chromium.org