New issue
Advanced search Search tips

Issue 707874 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 633330
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Build artifacts not available from external builders (first reported for ToT informational builders)

Project Member Reported by achuith@chromium.org, Apr 3 2017

Issue description

amd64-generic-tot-chromium-pfq-informational builder:
https://uberchromegw.corp.google.com/i/chromiumos.chromium/builders/amd64-generic-tot-chromium-pfq-informational

Successful build from Mar 30:
https://uberchromegw.corp.google.com/i/chromiumos.chromium/builders/amd64-generic-tot-chromium-pfq-informational/builds/11856

Link to artifacts:
https://storage.cloud.google.com/chromeos-image-archive/amd64-generic-tot-chromium-pfq-informational/R59-9415.0.0-b11856/index.html

Clicking on any of the artifacts fails with an error like:

{"error":{"errors":[{"domain":"global","reason":"badLockedDomainRequest","message":"Bad Locked Domain Request","debugInfo":"Error extracting locked domain from query string\ncom.google.api.server.core.Fault: ImmutableErrorDefinition{base=BAD_LOCKED_DOMAIN_REQUEST, category=USER_ERROR, cause=null, debugInfo=Error extracting locked domain from query string, domain=global, extendedHelp=null, httpHeaders={}, httpStatus=badRequest, internalReason=Reason{arguments={}, cause=null, code=null, createdByBackend=false, debugMessage=null, errorProtoCode=null, errorProtoDomain=null, filteredMessage=null, location=null, message=null, unnamedArguments=[]}, location=null, message=Bad Locked Domain Request, reason=badLockedDomainRequest, rpcCode=400} Bad Locked Domain Request: Error extracting locked domain from query string\n\tat com.google.api.server.responsesafety.ApiRequestUriCrypter.getEncryptedApiRequest(ApiRequestUriCrypter.java:195)\n\tat com.google.api.server.responsesafety.ApiRequestUriCrypter.unlock(ApiRequestUriCrypter.java:106)\n\tat com.google.api.server.responsesafety.LockedStrategy.lockedDomainInterceptorRequest(LockedStrategy.java:80)\n\tat com.google.api.server.responsesafety.LockedDomainInterceptor.processRequest(LockedDomainInterceptor.java:59)\n\tat com.google.api.server.core.intercept.AroundInterceptorWrapper.processRequest(AroundInterceptorWrapper.java:20)\n\tat com.google.api.server.stats.StatsBootstrap$InterceptorStatsRecorder.processRequest(StatsBootstrap.java:278)\n\tat com.google.api.server.core.intercept.Interceptions$AroundInterception.processRequest(Interceptions.java:159)\n\tat com.google.api.server.core.intercept.Interceptions$AroundInterception.invoke(Interceptions.java:135)\n\tat com.google.api.server.media.AbstractMediaClosure.continueRequest(AbstractMediaClosure.java:59)\n\tat com.google.api.server.media.batch.BatchAgent.continueRequest(BatchAgent.java:147)\n\tat com.google.api.server.media.batch.BatchAgent.onRequestReceived(BatchAgent.java:80)\n\tat com.google.uploader.agent.ScottyBatchAgent$ServiceParameters$1.handleRequest(ScottyBatchAgent.java:418)\n\tat com.google.net.rpc3.impl.server.RpcServerInternalContext.runRpcInApplication(RpcServerInternalContext.java:563)\n\tat com.google.net.rpc3.impl.server.RpcServerChannel$1$1.runInContext(RpcServerChannel.java:871)\n\tat com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:460)\n\tat com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:321)\n\tat com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:311)\n\tat com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:457)\n\tat com.google.api.server.thread.ThreadTrackers$ThreadTrackingRunnable.run(ThreadTrackers.java:126)\n\tat com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:453)\n\tat com.google.api.server.server.CommonModule$ContextCarryingExecutorService$1.runInContext(CommonModule.java:841)\n\tat com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:460)\n\tat com.google.tracing.CurrentContext.runInContext(CurrentContext.java:293)\n\tat com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:319)\n\tat com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:311)\n\tat com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:457)\n\tat com.google.gse.internal.DispatchQueueImpl$WorkerThread.run(DispatchQueueImpl.java:387)\n"}],"code":400,"message":"Bad Locked Domain Request"}}


 
Cc: pprabhu@chromium.org
Labels: -Pri-1 Pri-2
Owner: achuith@chromium.org
I can navigate to the artifacts link pointed above and from the build just fine.

Please make sure this isn't a credentials problem. If you do figure out what was wrong, please point out any UI improvements that may help.
Labels: -Pri-2 Pri-1
Owner: pprabhu@chromium.org
oops. Misread, you mean can't click on any of the artifacts. I see that now.
This isn't working for builds at least since March 7th across the pfq-information waterfall.

Looks like we changed where the artifacts link points to, but the informational bots didn't get udpated.

If you look at a pfq build, the artifacts link sends you directly to pantheon: https://uberchromegw.corp.google.com/i/chromeos/builders/arm-generic-chromium-pfq/builds/3305
Cc: dgarr...@chromium.org
So, the difference seems to be that the informational builders' artifacts are pointing to ..../<revision>/index.html (a file) vs the pfqs' artifacts are point to ..../<revision>/

We redirect the two to different locations, and only the first one seems to be broken.

+dgarrett for more magical information.
Summary: Build artifacts not available from external builders (first reported for ToT informational builders) (was: Build artifacts not available from TOT informational builders)
The difference is internal vs external.

Here's where we decide on the URLs: http://shortn/_6HipmkLAks

This means that for an unknown time now, external builders' artifacts links have been broken. Probably because GS changed some permissions enforcement policies?
Mergedinto: 633330
Status: Duplicate (was: Assigned)
It's a pretty old bug that I started on, but never seem to get time to finish.

Sign in to add a comment