Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • alpine-cloud-images alpine-cloud-images
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • cloudcloud
  • alpine-cloud-imagesalpine-cloud-images
  • Issues
  • #126
Closed
Open
Issue created Dec 28, 2021 by Jake Buchholz Göktürk@tomalokOwner

AWS images not working with CloudFormation

When attempting to use a new AWS image with CloudFormation (via Terraform) it fails with this error:

│ Error: error waiting for CloudFormation Stack creation: failed to create CloudFormation stack, rollback requested (ROLLBACK_COMPLETE): ["The following resource(s) failed to create: [devASGworkerA]. Rollback requested by user." "You must use a valid fully-formed launch template. The device 'xvda' is used in more than one block-device mapping (Service: AmazonAutoScaling; Status Code: 400; Error Code: ValidationError; Request ID: 49ca4896-1efa-467a-91a1-c07675b66448; Proxy: null)"]

Launching images on their own, however works. A quick search for similar error messages found this thread, similar problem experienced between Debian Jesse and Debian Stretch, the only difference is that the one that works specifies /dev/xvda instead of just xvda for block volume devices.

Fix is forthcoming

Edited Dec 28, 2021 by Jake Buchholz Göktürk
Assignee
Assign to
Time tracking