Cloud Build Error when deploying GAE

600 views
Skip to first unread message

Larry Schiefer

unread,
Feb 25, 2020, 9:33:01 AM2/25/20
to google-a...@googlegroups.com
Our project uses GAE standard, auto-scaling, Python 2.7. We deploy using gcloud and haven't changed anything regarding the way we deploy. However, now we are starting to see these types of errors when we deploy:

File upload done.
Updating service [default]...failed.                                                                
ERROR: (gcloud.app.deploy) Error Response: [9] Cloud build 42869100-9940-4821-8d40-3c52bf2fa268 status: FAILURE.
Build error details: Failed to download at least one file. Cannot continue.
.
Check the build log for errors: https://console.cloud.google.com/gcr/builds/42869100-9940-4821-8d40-3c52bf2fa268?project=XXXXXXXXXXXX

If we re-deploy (same command, same code) it then succeeds.  If we follow the link in the error message, it always shows "unable to find the resource" error.  Does anyone know why this is happening all of the sudden?

Gcloud details:
Google Cloud SDK 260.0.0
app-engine-python 1.9.86
app-engine-python-extras 1.9.86
bq 2.0.47
cloud-datastore-emulator 2.1.0
core 2019.08.23
gcloud
gsutil 4.42

Thanks,
Larry

Pierre-Yves (Google Cloud Support)

unread,
Feb 25, 2020, 1:41:00 PM2/25/20
to Google App Engine
Hello Larry,

Could you please provide the full console output after the re-try? This may provide a hint as to which files were unsuccessfully downloaded in the first try.

Larry Schiefer

unread,
Feb 25, 2020, 2:13:53 PM2/25/20
to google-a...@googlegroups.com
Hi Pierre,

Thank you for responding and asking for more details.

Below is the full output from the 2nd run (project ID removed):

Services to deploy:

descriptor:      [/Users/larrys/tmp/build/project/backend/app.yaml]
source:          [/Users/larrys/tmp/build/project/backend]
target project:  [XXXXXXXXXX]
target service:  [default]
target version:  [20200225t065208]
target url:      [https://XXXXXXXXXX.appspot.com]


Configurations to update:

descriptor:      [/Users/larrys/tmp/build/project/backend/index.yaml]
type:            [datastore indexes]
target project:  [XXXXXXXXXX]


descriptor:      [/Users/larrys/tmp/build/project/backend/queue.yaml]
type:            [task queues]
target project:  [XXXXXXXXXX]


Do you want to continue (Y/n)?  y

Beginning deployment of service [default]...
╔════════════════════════════════════════════════════════════╗
╠═ Uploading 1 file to Google Cloud Storage                 ═╣
╚════════════════════════════════════════════════════════════╝
File upload done.
Updating service [default]...done.                                                                  
Setting traffic split for service [default]...done.                                                  
Deployed service [default] to [https://XXXXXXXXXX.appspot.com]
Updating config [index]...done.                                                                      
Updating config [queue]...done.                                                                      

Task queues have been updated.

Visit the Cloud Platform Console Task Queues page to view your queues and cron jobs.

Indexes are being rebuilt. This may take a moment.

You can stream logs from the command line by running:
  $ gcloud app logs tail -s default

To view your application in the web browser run:
  $ gcloud app browse --project=XXXXXXXXXX



--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/cb6a7625-18cb-4cb6-97eb-2f8b844a7ac4%40googlegroups.com.


--

Katayoon (Cloud Platform Support)

unread,
Feb 28, 2020, 9:38:43 AM2/28/20
to Google App Engine
Hi Larry,

I recommend to report the issue in the GCP Issue Tracker and provide us with the REDACTED output of the command you are using to deploy your app along with the "--verbosity" flag set to DEBUG; and also the output of the "gcloud info --anonymize" so that we would be able to investigate the issue.
Reply all
Reply to author
Forward
0 new messages