Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43586

CloudFormation stack is not deleted when creation fails

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • pipeline-aws-plugin
    • None

      After a CloudFormation stack fails to create, it can no longer be used but is not deleted by the plugin. This causes all future updates to fail with a "<stack name> is in ROLLBACK_COMPLETE state and can not be updated." error.

          [JENKINS-43586] CloudFormation stack is not deleted when creation fails

          Thorsten Hoeger added a comment -

          Hi, this is indeed an interesting thing. How would you recommend the plugin handles this case?

          Thorsten Hoeger added a comment - Hi, this is indeed an interesting thing. How would you recommend the plugin handles this case?

          Roch Devost added a comment -

          I don't know if it's the best way, but I know the serverless framework handles this by basically creating an empty stack first, and then updates it. This way, creation never fails so it is possible to update again after failure since the failure is now on update and not on create.

          Roch Devost added a comment - I don't know if it's the best way, but I know the serverless  framework handles this by basically creating an empty stack first, and then updates it. This way, creation never fails so it is possible to update again after failure since the failure is now on update and not on create.

            hoegertn Thorsten Hoeger
            rochdev Roch Devost
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: