An error occurred (ValidationError) when calling the CreateChangeSet operation … is in ROLLBACK_COMPLETE...
I understand why AWS leaves a stack if a deploy fails so you can see the error.
But is there a force switch so i can redeploy and have aws delete the stack for me? Otherwise I have to delete it myself.
amazon-web-services amazon-cloudformation
add a comment |
I understand why AWS leaves a stack if a deploy fails so you can see the error.
But is there a force switch so i can redeploy and have aws delete the stack for me? Otherwise I have to delete it myself.
amazon-web-services amazon-cloudformation
add a comment |
I understand why AWS leaves a stack if a deploy fails so you can see the error.
But is there a force switch so i can redeploy and have aws delete the stack for me? Otherwise I have to delete it myself.
amazon-web-services amazon-cloudformation
I understand why AWS leaves a stack if a deploy fails so you can see the error.
But is there a force switch so i can redeploy and have aws delete the stack for me? Otherwise I have to delete it myself.
amazon-web-services amazon-cloudformation
amazon-web-services amazon-cloudformation
asked Jun 18 '18 at 14:39


red888red888
4,65474497
4,65474497
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Not sure how you are creating CFT stack but if you are using CLI, you can specify --on-failure DELETE
option which will delete the stack if the deployment fails.
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
There is noforce
switch kind of a thing but if you are using CLI then try todelete
the stack and thencreate
it.
– Asdfg
Jun 18 '18 at 15:02
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
add a comment |
This has happened once in a Buildkite pipeline, and after manually deleting the stack (Status: DELETE_COMPLETE) was able to re-create/update via the pipeline.
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%2f50911962%2fan-error-occurred-validationerror-when-calling-the-createchangeset-operation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Not sure how you are creating CFT stack but if you are using CLI, you can specify --on-failure DELETE
option which will delete the stack if the deployment fails.
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
There is noforce
switch kind of a thing but if you are using CLI then try todelete
the stack and thencreate
it.
– Asdfg
Jun 18 '18 at 15:02
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
add a comment |
Not sure how you are creating CFT stack but if you are using CLI, you can specify --on-failure DELETE
option which will delete the stack if the deployment fails.
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
There is noforce
switch kind of a thing but if you are using CLI then try todelete
the stack and thencreate
it.
– Asdfg
Jun 18 '18 at 15:02
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
add a comment |
Not sure how you are creating CFT stack but if you are using CLI, you can specify --on-failure DELETE
option which will delete the stack if the deployment fails.
Not sure how you are creating CFT stack but if you are using CLI, you can specify --on-failure DELETE
option which will delete the stack if the deployment fails.
answered Jun 18 '18 at 14:52
AsdfgAsdfg
4,4311865123
4,4311865123
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
There is noforce
switch kind of a thing but if you are using CLI then try todelete
the stack and thencreate
it.
– Asdfg
Jun 18 '18 at 15:02
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
add a comment |
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
There is noforce
switch kind of a thing but if you are using CLI then try todelete
the stack and thencreate
it.
– Asdfg
Jun 18 '18 at 15:02
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
yeah but like i said it remains so you can look at the error. Id prefer a force switch that deletes it because then I can choose to look at the error if i want or just re-run the command
– red888
Jun 18 '18 at 14:59
There is no
force
switch kind of a thing but if you are using CLI then try to delete
the stack and then create
it.– Asdfg
Jun 18 '18 at 15:02
There is no
force
switch kind of a thing but if you are using CLI then try to delete
the stack and then create
it.– Asdfg
Jun 18 '18 at 15:02
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
thats what i do now. just wasn't sure if this was really the only way- i guess so :(
– red888
Jun 18 '18 at 15:03
add a comment |
This has happened once in a Buildkite pipeline, and after manually deleting the stack (Status: DELETE_COMPLETE) was able to re-create/update via the pipeline.
add a comment |
This has happened once in a Buildkite pipeline, and after manually deleting the stack (Status: DELETE_COMPLETE) was able to re-create/update via the pipeline.
add a comment |
This has happened once in a Buildkite pipeline, and after manually deleting the stack (Status: DELETE_COMPLETE) was able to re-create/update via the pipeline.
This has happened once in a Buildkite pipeline, and after manually deleting the stack (Status: DELETE_COMPLETE) was able to re-create/update via the pipeline.
answered Nov 21 '18 at 7:32
Dinesh HalpageDinesh Halpage
315
315
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.
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%2f50911962%2fan-error-occurred-validationerror-when-calling-the-createchangeset-operation%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