Introduction
A stack configuration may become stuck in a "spinning" or queued state, preventing further progress or cancellation. This guide outlines steps to resolve this issue effectively.
Expected Outcome
The stack configuration will exit the spinning state and begin processing a new configuration successfully, without requiring a forced cancellation or extended waiting period.
Prerequisites
Access to the deployment or infrastructure management platform (for example, Terraform Cloud, HCP, or similar).
Permissions to manage and update stack configurations.
An understanding of how to fetch or push new configurations in the environment.
Use Case
This approach applies when a stack configuration remains indefinitely queued or spinning, and standard cancellation methods are unavailable or ineffective.
Procedure
Step 1: Access the Stack
Locate the affected stack that is stuck in a spinning or queued state.
Step 2: Prepare a Fresh Configuration
Prepare a fresh configuration in the version control system (VCS) or local environment. This may include making a minimal, non-functional change (such as adding a comment) to ensure a new configuration can be fetched.
Step 3: Push or Fetch the New Configuration
Push the fresh configuration to the stack or trigger a fetch operation from the VCS
Step 4: Monitor Status
After the new configuration is fetched, the previously queued or stuck prepare operation should be canceled automatically. Monitor the stack to confirm that it begins processing the new configuration.
Step 5: Verify Resolution
Verify that the stack has exited the spinning state and has successfully completed or progressed to the appropriate stage.