HttpBadRequestError when deploy app using gcloud

380 views
Skip to first unread message

Hoang Van

unread,
Aug 28, 2018, 11:01:07 AM8/28/18
to Google App Engine
i using bellow command to deploy php app to app engine:
gcloud app deploy --promote --project test12 app-live.yaml --log-http --verbosity=debug

My app-live.yaml file: https://shrib.com/?v=nc#uUXDedcjuzf-P28OdKJ5

but show this error:

HttpBadRequestError: HttpError accessing https://appengine.googleapis.com/v1/apps/ads-clickgs/services/default/versions?alt=json: response: <{'status': '400', 'content-length': '252', 'x-xss-protection': '1; mode=block', 'x-content-type-options': 'nosniff', 'transfer-encoding': 'chunked', 'vary': 'Origin, X-Origin, Referer', 'server': 'ESF', '-content-encoding': 'gzip', 'cache-control': 'private', 'date': 'Tue, 28 Aug 2018 04:44:34 GMT', 'x-frame-options': 'SAMEORIGIN', 'alt-svc': 'quic=":443"; ma=2592000; v="44,43,39,35"', 'content-type': 'application/json; charset=UTF-8'}>, content <{ "error": { "code": 400, "message": "Please update to the latest version of gcloud. If you are using the API directly, please provide a value for version.entrypoint.shell. This can be an empty value.", "status": "INVALID_ARGUMENT" } }

i searched on google but not found any suggestion. thanks

Attila-Mihaly Balazs

unread,
Aug 29, 2018, 12:33:06 AM8/29/18
to Google App Engine
Have you tried updating gcloud as suggested by the error message?

Attila

sami...@google.com

unread,
Aug 29, 2018, 9:49:32 AM8/29/18
to Google App Engine

Looking at your issue and the error message, it seems like your gcloud components are not updated to the latest version. To update all installed components to the latest version please try the following command on your environment:

$gcloud components update


I would recommend going through the following article which provides step-by-step instruction on how to update gcloud components to the latest version or the version that you prefer.


Hoang Van

unread,
Aug 29, 2018, 11:04:12 AM8/29/18
to Google App Engine
i fixed it by add app.yaml, the default entrypoint.
But now i got this error:
"error": {
        "message": "An internal error occurred.",
        "code": 13
    }
DEBUG: Operation [apps/ads-clickgs/operations/376e07d2-555f-4517-be18-97a4c6c08ac0] not complete. Waiting to retry.
Updating service [web]...⠛DEBUG: Operation [apps/ads-clickgs/operations/376e07d2-555f-4517-ce18-97a4c6c08ac1] not complete. Waiting to retry.
Updating service [web]...⠛DEBUG: Operation [apps/ads-clickgs/operations/376e07d2-555f-4517-ce18-97a4c6c08ac1] not complete. Waiting to retry.
Updating service [web]...⠛DEBUG: Operation [apps/ads-clickgs/operations/376e07d2-555f-4517-ce18-97a4c6c08ac1] not complete. Waiting to retry.
Updating service [web]...⠹DEBUG: Operation [apps/ads-clickgs/operations/376e07d2-555f-4517-ce18-97a4c6c08ac1] not complete. Waiting to retry.
Updating service [web]...⠼DEBUG: Operation [apps/ads-clickgs/operations/376e07d2-555f-4517-ce18-97a4c6c08ac1] not complete

sami...@google.com

unread,
Aug 30, 2018, 4:54:42 PM8/30/18
to Google App Engine

Hello Hoang,

I would suggest deploying the app from the Cloud Shell by going through the following article. This way the deployment will be independent of the local environment. This is the documentation that explains the app.yaml configuration for PHP 7.2 Application. This way you would be able to verify which files or folders were different from the setup that you have created on your Cloud Shell environment and the local environment.  


There is currently an issue reported on the issuetracker with the same error code when trying to deploy to Google App Engine a directory with more than a thousand files. You can definitely request an investigation on issuetracker if you think your issue is not the same. Google group is usually meant for general product discussion only. So I would recommend reporting the issue in Google Public Issue Tracker to notify the gcloud team about the error.  

Hoang Van

unread,
Aug 31, 2018, 11:27:20 AM8/31/18
to Google App Engine
thank, i will read it
Reply all
Reply to author
Forward
0 new messages