Fix the cautotest googlestorage rewrite rule
Reported by
jrbarnette@chromium.org,
Mar 23 2016
|
|||||||
Issue description
Recently, the rewrite rule in apache/conf/site-misc-directives
started producing frequent, sporadic failures.
The history of the failure, and what was learned can be seen
here:
/b2/27653354
The upshot is that the rewrite rule is wrong. That ticket
suggests a specific rewrite rule. However, from the last
time that we had a bug like this, we were recommended this
link:
https://cloud.google.com/storage/docs/reference-uris
It seems we didn't follow the advice; it seems our rewrite
rule should use this base URI:
storage.googleapis.com/<bucket>/[<object>]
,
Mar 23 2016
... And for the record, here's the bug with the URI
documentation that we seem to have ignored:
b2/17318944
,
Mar 23 2016
... except that testing a URL of the given form shows a failure. :-(
,
Mar 23 2016
OK. Reading the document further, I find this format
to be the one to follow:
https://storage.cloud.google.com/<bucket>/<object>
,
Mar 23 2016
... which is _exactly_ the URL we're using today.
,
Mar 28 2016
,
Mar 28 2016
,
Mar 30 2016
so the link we should be using is https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results but I have a feeling that's just for us given the corp.google.com, I'll press Andres (GCS contact) on whether that's the right link and if the documentation should be updated.
,
Apr 6 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/a78d42173eb7426ff29ba6d887e05d2a48f2e93a commit a78d42173eb7426ff29ba6d887e05d2a48f2e93a Author: Kevin Cheng <kevcheng@chromium.org> Date: Wed Mar 30 23:33:14 2016 [autotest] Fix up retrieve_logs.cgi to use pantheon link. BUG= chromium:597135 TEST=locally test link. Change-Id: Ib02d1c4e795dd6de0eb8f43d4fb87ae18066a665 Reviewed-on: https://chromium-review.googlesource.com/336540 Commit-Queue: Kevin Cheng <kevcheng@chromium.org> Tested-by: Kevin Cheng <kevcheng@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/a78d42173eb7426ff29ba6d887e05d2a48f2e93a/tko/retrieve_logs.cgi
,
Apr 6 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/b4a619cfbb2a3e151157d12faa0a2b7c8202bb56 commit b4a619cfbb2a3e151157d12faa0a2b7c8202bb56 Author: Dan Shi <dshi@google.com> Date: Wed Apr 06 17:38:04 2016 [autotest] Update RewriteRule to direct to correct GS link BUG=b:27653354, chromium:597135 TEST=in chromeos-server14 Change-Id: I547569658bdedc3038e0e86c41f42e400fa072d2 Reviewed-on: https://chromium-review.googlesource.com/337344 Reviewed-by: Kevin Cheng <kevcheng@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> Commit-Queue: Dan Shi <dshi@google.com> Tested-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/b4a619cfbb2a3e151157d12faa0a2b7c8202bb56/apache/conf/site-misc-directives
,
Apr 22 2016
,
Apr 27 2016
,
Apr 27 2016
This is happening for links to VMTest results on builders, too. Should the same redirect fix the problem? E.g., if you click on the link "vm_test_results_1" of this build https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-incremental/builds/8440, you will get "Not Found You are getting this message because you have a Debug IP address. External clients only get "Not Found""
,
May 23 2016
Bulk verified |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jrbarnette@chromium.org
, Mar 23 2016