Cold deploy fails

Describe the issue

Followed the getting start guide and the deploy part just fails. I’ve included a full log of my shell below.

Steps to reproduce Steps to reproduce the behavior:

1. npm init @architect mocked
2. cd mocked
3. npx arc deploy
4. Then I got the errors

full log

$ npx arc deploy                                                     
         App ⌁ mocked
      Region ⌁ us-west-2
     Profile ⌁ default
     Version ⌁ Architect 10.7.0
         cwd ⌁ /Users/remy/dev/mocked
✓ Hydrate Finished checks, nothing to hydrate
⚬ Deploy Creating new private deployment bucket: mocked-cfn-deployments-6d101
⚬ Deploy Initializing deployment
| Stack … MockedStaging
| Bucket … mocked-cfn-deployments-6d101
⚬ Deploy Created deployment templates
✓ Deploy Generated CloudFormation deployment
Uploading to 6fa6d458959c1b3f03c7c62cc94d778d.template  5800 / 5800.0  (100.00%)
Waiting for changeset to be created…
Waiting for stack create/update to complete
Failed to create/update the stack. Run the following command
to fetch the list of events leading up to the failure
aws cloudformation describe-stack-events --stack-name MockedStaging
Uploading to 6fa6d458959c1b3f03c7c62cc94d778d.template  5800 / 5800.0  (100.00%)
Waiting for changeset to be created…
Waiting for stack create/update to complete
Failed to create/update the stack. Run the following command
to fetch the list of events leading up to the failure
aws cloudformation describe-stack-events --stack-name MockedStaging
at ChildProcess.<anonymous> (/Users/remy/dev/mocked/node_modules/@architect/deploy/src/sam/utils/spawn.js:23:16)
at ChildProcess.emit (node:events:513:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1091:16)
at Socket.<anonymous> (node:internal/child_process:449:11)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at Pipe.<anonymous> (node:net:313:12)

$ aws cloudformation describe-stack-events --stack-name MockedStaging
An error occurred (ValidationError) when calling the DescribeStackEvents operation: Stack [MockedStaging] does not exist

Desktop Please complete the following information (if appropriate):

• OS: macOS Big Sur 11.7 (20G817)

[remy]

Okay, solved it (appreciate many/all of you aren’t on the UK TZ) - found cloudformation in AWS and deleted the things I found - reployed and it went up.

Cheers so much.

I’m fairly sure the original issue was down to my using Leapp to change my profiles. Lesson learnt - I need to stick to the CLI where I’m actually more effective!

[remy]

Okay, I think I’ve gotten further. I was using Leapp and I’m fairly sure it was messing things up. So I trashed it and ran aws configure again and the deploy got further.

But now I wonder if the deploy has gotten in a half baked state…

Details

$ npx arc deploy
         App ⌁ mocked
      Region ⌁ us-west-2
     Profile ⌁ arc.code
     Version ⌁ Architect 10.7.0
         cwd ⌁ /Users/remy/dev/mocked

✓ Hydrate Finished checks, nothing to hydrate
⚬ Deploy Initializing deployment
  | Stack ... MockedStaging
  | Bucket .. mocked-cfn-deployments-6d101
⚬ Deploy Created deployment templates
✓ Deploy Generated CloudFormation deployment
Uploading to 66450ca3d0389812ed4a6f6beba5366d.template  5800 / 5800.0  (100.00%)
An error occurred (ValidationError) when calling the CreateChangeSet operation: Stack:arn:aws:cloudformation:us-west-2:596019491244:stack/MockedStaging/9f91f240-456c-11ed-b481-0284f74e1693 is in ROLLBACK_COMPLETE state and can not be updated.

Uploading to 66450ca3d0389812ed4a6f6beba5366d.template  5800 / 5800.0  (100.00%)
An error occurred (ValidationError) when calling the CreateChangeSet operation: Stack:arn:aws:cloudformation:us-west-2:596019491244:stack/MockedStaging/9f91f240-456c-11ed-b481-0284f74e1693 is in ROLLBACK_COMPLETE state and can not be updated.

    at ChildProcess.<anonymous> (/Users/remy/dev/mocked/node_modules/@architect/deploy/src/sam/utils/spawn.js:23:16)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:489:12)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:513:28)
    at Socket.emit (node:domain:489:12)
    at Pipe.<anonymous> (node:net:313:12)

Any ideas how I can reset the aws state?