Error while deploying Flask app on Google Cloud Platform
Getting this error when I am trying to deploy to google app engine: ERROR: (gcloud.app.deploy) Error Response: [3]. This is my first trial deployment of a Flask app on GCP, so I am not sure how to handle this.
ERROR: (gcloud.app.deploy) Error Response: [3] The following errors occurred while copying files to App Engine:
File https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91 failed with: Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".
Details: [
[
{
"@type": "type.googleapis.com/google.rpc.ResourceInfo",
"description": "Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".",
"resourceName": "https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91",
"resourceType": "file"
}
]
]
There are a total of 10 similar errors for 10 different resource names that have exactly the same description. What does conflicting SHA1 sum for file mean? I tried deleting the staging bucket to remove the temporary files with the same name as the resource name (02aad073e7e7b22302caeca9aa3d6aaf227d7d9 in this case) causing the error, but that doesn't seem to work.
python google-app-engine deployment google-cloud-platform flask-sqlalchemy
add a comment |
Getting this error when I am trying to deploy to google app engine: ERROR: (gcloud.app.deploy) Error Response: [3]. This is my first trial deployment of a Flask app on GCP, so I am not sure how to handle this.
ERROR: (gcloud.app.deploy) Error Response: [3] The following errors occurred while copying files to App Engine:
File https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91 failed with: Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".
Details: [
[
{
"@type": "type.googleapis.com/google.rpc.ResourceInfo",
"description": "Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".",
"resourceName": "https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91",
"resourceType": "file"
}
]
]
There are a total of 10 similar errors for 10 different resource names that have exactly the same description. What does conflicting SHA1 sum for file mean? I tried deleting the staging bucket to remove the temporary files with the same name as the resource name (02aad073e7e7b22302caeca9aa3d6aaf227d7d9 in this case) causing the error, but that doesn't seem to work.
python google-app-engine deployment google-cloud-platform flask-sqlalchemy
1
This error about conflicting SHA1 sum is usually due to gcloud while deploying the application, is trying to upload a SHA1 sum resource file that is already in your staging bucket and creates a conflict with the one being uploaded. Since you mentioned you deleted the staging bucket and did not solve the issue, could you please run “gcloud app deploy --verbosity=debug” and update your answer with the output? this should provide more information about the error.
– David
Nov 22 '18 at 15:07
add a comment |
Getting this error when I am trying to deploy to google app engine: ERROR: (gcloud.app.deploy) Error Response: [3]. This is my first trial deployment of a Flask app on GCP, so I am not sure how to handle this.
ERROR: (gcloud.app.deploy) Error Response: [3] The following errors occurred while copying files to App Engine:
File https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91 failed with: Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".
Details: [
[
{
"@type": "type.googleapis.com/google.rpc.ResourceInfo",
"description": "Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".",
"resourceName": "https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91",
"resourceType": "file"
}
]
]
There are a total of 10 similar errors for 10 different resource names that have exactly the same description. What does conflicting SHA1 sum for file mean? I tried deleting the staging bucket to remove the temporary files with the same name as the resource name (02aad073e7e7b22302caeca9aa3d6aaf227d7d9 in this case) causing the error, but that doesn't seem to work.
python google-app-engine deployment google-cloud-platform flask-sqlalchemy
Getting this error when I am trying to deploy to google app engine: ERROR: (gcloud.app.deploy) Error Response: [3]. This is my first trial deployment of a Flask app on GCP, so I am not sure how to handle this.
ERROR: (gcloud.app.deploy) Error Response: [3] The following errors occurred while copying files to App Engine:
File https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91 failed with: Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".
Details: [
[
{
"@type": "type.googleapis.com/google.rpc.ResourceInfo",
"description": "Conflicting SHA1 sum for file. Expected "e0962ea6_8c330ca4_d3fff179_b1f68032_ef476e8e" but received "02aad073_e7e7b223_02caeca9_aa3d6aaf_227d7d91".",
"resourceName": "https://storage.googleapis.com/staging.<app_id>.appspot.com/02aad073e7e7b22302caeca9aa3d6aaf227d7d91",
"resourceType": "file"
}
]
]
There are a total of 10 similar errors for 10 different resource names that have exactly the same description. What does conflicting SHA1 sum for file mean? I tried deleting the staging bucket to remove the temporary files with the same name as the resource name (02aad073e7e7b22302caeca9aa3d6aaf227d7d9 in this case) causing the error, but that doesn't seem to work.
python google-app-engine deployment google-cloud-platform flask-sqlalchemy
python google-app-engine deployment google-cloud-platform flask-sqlalchemy
edited Dec 10 '18 at 1:36
Jofre
1,467915
1,467915
asked Nov 21 '18 at 14:49
Rajesh
12
12
1
This error about conflicting SHA1 sum is usually due to gcloud while deploying the application, is trying to upload a SHA1 sum resource file that is already in your staging bucket and creates a conflict with the one being uploaded. Since you mentioned you deleted the staging bucket and did not solve the issue, could you please run “gcloud app deploy --verbosity=debug” and update your answer with the output? this should provide more information about the error.
– David
Nov 22 '18 at 15:07
add a comment |
1
This error about conflicting SHA1 sum is usually due to gcloud while deploying the application, is trying to upload a SHA1 sum resource file that is already in your staging bucket and creates a conflict with the one being uploaded. Since you mentioned you deleted the staging bucket and did not solve the issue, could you please run “gcloud app deploy --verbosity=debug” and update your answer with the output? this should provide more information about the error.
– David
Nov 22 '18 at 15:07
1
1
This error about conflicting SHA1 sum is usually due to gcloud while deploying the application, is trying to upload a SHA1 sum resource file that is already in your staging bucket and creates a conflict with the one being uploaded. Since you mentioned you deleted the staging bucket and did not solve the issue, could you please run “gcloud app deploy --verbosity=debug” and update your answer with the output? this should provide more information about the error.
– David
Nov 22 '18 at 15:07
This error about conflicting SHA1 sum is usually due to gcloud while deploying the application, is trying to upload a SHA1 sum resource file that is already in your staging bucket and creates a conflict with the one being uploaded. Since you mentioned you deleted the staging bucket and did not solve the issue, could you please run “gcloud app deploy --verbosity=debug” and update your answer with the output? this should provide more information about the error.
– David
Nov 22 '18 at 15:07
add a comment |
1 Answer
1
active
oldest
votes
You have 2 different files which are uploaded with the same name.
To identify if this is actually an issue with your deployment or with the staging bucket, create a new clean bucket and try the deployment again using that new bucket as the staging bucket:
$ gsutil mb gs://new-staging-bucket
$ gcloud app deploy --bucket gs://new-staging-bucket
If you get the same error with a clean bucket, then you're somehow uploading several different files with the same name during deployment.
If using a clean bucket works, then the issue is with the staging bucket that you're using during your deployment.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414633%2ferror-while-deploying-flask-app-on-google-cloud-platform%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have 2 different files which are uploaded with the same name.
To identify if this is actually an issue with your deployment or with the staging bucket, create a new clean bucket and try the deployment again using that new bucket as the staging bucket:
$ gsutil mb gs://new-staging-bucket
$ gcloud app deploy --bucket gs://new-staging-bucket
If you get the same error with a clean bucket, then you're somehow uploading several different files with the same name during deployment.
If using a clean bucket works, then the issue is with the staging bucket that you're using during your deployment.
add a comment |
You have 2 different files which are uploaded with the same name.
To identify if this is actually an issue with your deployment or with the staging bucket, create a new clean bucket and try the deployment again using that new bucket as the staging bucket:
$ gsutil mb gs://new-staging-bucket
$ gcloud app deploy --bucket gs://new-staging-bucket
If you get the same error with a clean bucket, then you're somehow uploading several different files with the same name during deployment.
If using a clean bucket works, then the issue is with the staging bucket that you're using during your deployment.
add a comment |
You have 2 different files which are uploaded with the same name.
To identify if this is actually an issue with your deployment or with the staging bucket, create a new clean bucket and try the deployment again using that new bucket as the staging bucket:
$ gsutil mb gs://new-staging-bucket
$ gcloud app deploy --bucket gs://new-staging-bucket
If you get the same error with a clean bucket, then you're somehow uploading several different files with the same name during deployment.
If using a clean bucket works, then the issue is with the staging bucket that you're using during your deployment.
You have 2 different files which are uploaded with the same name.
To identify if this is actually an issue with your deployment or with the staging bucket, create a new clean bucket and try the deployment again using that new bucket as the staging bucket:
$ gsutil mb gs://new-staging-bucket
$ gcloud app deploy --bucket gs://new-staging-bucket
If you get the same error with a clean bucket, then you're somehow uploading several different files with the same name during deployment.
If using a clean bucket works, then the issue is with the staging bucket that you're using during your deployment.
answered Dec 9 '18 at 23:16
Jofre
1,467915
1,467915
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414633%2ferror-while-deploying-flask-app-on-google-cloud-platform%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This error about conflicting SHA1 sum is usually due to gcloud while deploying the application, is trying to upload a SHA1 sum resource file that is already in your staging bucket and creates a conflict with the one being uploaded. Since you mentioned you deleted the staging bucket and did not solve the issue, could you please run “gcloud app deploy --verbosity=debug” and update your answer with the output? this should provide more information about the error.
– David
Nov 22 '18 at 15:07