Cloud Function build error - go113_20200924_20_RC00

88 views
Skip to first unread message

Črtomir Majer

unread,
Sep 28, 2020, 4:10:29 PM9/28/20
to Google App Engine
I can no longer deploy my Cloud Function using a commit from ~3 days ago that was deployed successfully at that time. From the logs, I can see there's a different image used to build the function - go113_20200924_20_RC00. The error I get is:

ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Build failed: package cloud.google.com/go/functions/metadata: /workspace/src/cloud.google.com/go exists but /workspace/src/cloud.google.com/go/.git does not - stale checkout?
package go.opencensus.io/plugin/ochttp: /workspace/src/go.opencensus.io exists but /workspace/src/go.opencensus.io/.git does not - stale checkout?
        /usr/local/go/src/go.opencensus.io/plugin/ochttp/propagation/tracecontext (from $GOROOT)
        /workspace/src/go.opencensus.io/plugin/ochttp/propagation/tracecontext (from $GOPATH); Error ID: 1093f764

Shawn Wu

unread,
Sep 29, 2020, 4:12:46 PM9/29/20
to Google App Engine
if you deploy by using gcloud, please ensure the command is correct. the error message seems to indicate  command invalid.

Sterling Ramroach

unread,
Sep 29, 2020, 7:38:37 PM9/29/20
to Google App Engine
From 3 days ago (25-09-2020) my images that are deployed via commits stopped working as expected also. The deploys were successful but not the function to run a pystan model. I am only sharing this because I also think something changed 3 days ago but I can't figure out what. Prior to 3 days ago my deploys and models worked fine. 

Olu

unread,
Sep 30, 2020, 10:33:06 AM9/30/20
to Google App Engine
Checking our internal issue tracker, there is really no system-wide issue or change reported for Cloud Functions. I think to better evaluate the issue you are observing, you should contact the GCP Support Engineers[1] or if you think this issue is a bug, then open an issue using this link[2].

This way a GCP Support engineer would be able to work closely with you, reviewing logs to determine exactly what may be the cause of the issue.


Reply all
Reply to author
Forward
0 new messages