search

aws-amplify / amplify-cli

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
Apache License 2.0
2.81k stars 821 forks source link

Resource is not in the state stackUpdateComplete #82

Closed haverchuck closed 2 years ago

haverchuck commented 6 years ago

Do you want to request a feature or report a bug? Bug

What is the current behavior? After enabling analytics with auth, and pushing, the user is not able to runamplify auth update(and select default configuration) and then push without receiving the error"Resource is not in the state stackUpdateComplete". When the auth stack in cloudformation is inspected, the following error is observed: Parameters: [autoVerifiedAttributes, smsVerificationMessage, userpoolClientReadAttributes, mfaTypes, emailVerificationSubject, useDefault, userpoolClientGenerateSecret, mfaConfiguration, userpoolClientLogPolicy, smsAuthenticationMessage, roleExternalId, mfaLambdaLogPolicy, passwordPolicyMinLength, userPoolName, policyName, userpoolClientName, userpoolClientLambdaPolicy, mfaLambdaIAMPolicy, mfaPassRolePolicy, emailVerificationMessage, userpoolClientRefreshTokenValidity, userpoolClientSetAttributes, requiredAttributes, roleName, passwordPolicyCharacters, userpoolClientLambdaRole, defaultPasswordPolicy, mfaLambdaRole] must have values. (These are userpool attributes, which should all be added since the default auth configuration is adding a userpool to the identity pool that was created when analytics was enabled.)

However, the user's auth resources's parameters.json file appears to contain all of these parameters, and their cloudformation template appears to be formed correctly.

UPDATE: This issue also occurs when running amplify api add, but with the api stacking being affected instead of the auth stack: Parameters: [MutationCreateNoteResponse, QueryListNotesResponse, QueryGetNoteRequest, MutationDeleteNoteRequest, QueryGetNoteResponse, QueryListNotesRequest, MutationCreateNoteRequest, schemaGraphql, MutationDeleteNoteResponse, MutationUpdateNoteRequest, MutationUpdateNoteResponse] must have values

Steps to reproduce the issue: This issue occurs intermittently, and the repro steps listed here are provisional. The precise circumstances causing this error are not yet know.

  1. amplify init (iOS project)
  2. amplify analytics add (w/ auth)
  3. amplify push (successful)
  4. amplify auth update (select default configuration)
  5. amplify auth push

What is the expected behavior? Auth stack should update appropriately.

Additional environment details

haverchuck commented 6 years ago

Possibly caused by use of experimental amplify delete feature in project directory prior to re-running amplify init.

rygo6 commented 6 years ago

I have this issue too.

my log

ryan@ryan-ubuntu:~/Developer/myappclone$ amplify push
| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | myapp         | Update    | awscloudformation |
? Are you sure you want to continue? true
⠋ Updating resources in the cloud. This may take a few minutes...
GraphQL schema compiled successfully. Edit your schema at /home/ryan/Developer/myappclone/amplify/backend/api/myapp/schema.graphql
⠦ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:36 GMT-0500 (CDT) User Initiated                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      
UPDATE_IN_PROGRESS          apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:40 GMT-0500 (CDT)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     
UPDATE_FAILED               apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:40 GMT-0500 (CDT) Parameters: [MutationDeletePostResponse, MutationDeleteBlogResponse, QueryListCommentsResponse, MutationDeleteBlogRequest, MutationUpdateCommentRequest, PostBlogResponse, MutationCreatePostRequest, QueryGetCommentRequest, MutationUpdatePostRequest, MutationDeleteCommentRequest, CommentPostRequest, QueryListBlogsResponse, MutationUpdateCommentResponse, PostCommentsResponse, MutationCreatePostResponse, QueryGetBlogResponse, MutationCreateBlogResponse, QueryGetPostResponse, MutationCreateCommentRequest, CommentPostResponse, MutationUpdatePostResponse, QueryGetCommentResponse, MutationUpdateBlogResponse, MutationDeletePostRequest, QueryGetBlogRequest, QueryListPostsResponse, QueryListCommentsRequest, BlogPostsResponse, MutationCreateBlogRequest, BlogPostsRequest, QueryGetPostRequest, MutationUpdateBlogRequest, PostBlogRequest, MutationCreateCommentResponse, QueryListPostsRequest, QueryListBlogsRequest, MutationDeleteCommentResponse, PostCommentsRequest] must have values
UPDATE_ROLLBACK_IN_PROGRESS myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:41 GMT-0500 (CDT) The following resource(s) failed to update: [apimyapp].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             
⠙ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:50 GMT-0500 (CDT) 
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:50 GMT-0500 (CDT) 
UPDATE_IN_PROGRESS                           apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:51 GMT-0500 (CDT) 
UPDATE_COMPLETE                              apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:52 GMT-0500 (CDT) 
UPDATE_ROLLBACK_COMPLETE                     myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:52 GMT-0500 (CDT) 
⠧ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
rygo6 commented 6 years ago

Also I get this error:

ryan@ryan-ubuntu:~/Developer/my-app$ amplify push
| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | myapp         | Update    | awscloudformation |
? Are you sure you want to continue? true
⠋ Updating resources in the cloud. This may take a few minutes...
GraphQL schema compiled successfully. Edit your schema at /home/ryan/Developer/my-app/amplify/backend/api/myapp/schema.graphql
⠏ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS                           myapp-20180830150843 AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:35 GMT-0500 (CDT) User Initiated                                                                                                                                                                                                                                                                                          
UPDATE_IN_PROGRESS                           apimyapp             AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:39 GMT-0500 (CDT)                                                                                                                                                                                                                                                                                                         
UPDATE_FAILED                                apimyapp             AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:40 GMT-0500 (CDT) Parameters: [MutationDeleteTodoResponse, QueryGetTodoResponse, MutationUpdateTodoResponse, QueryListTodosResponse, MutationUpdateTodoRequest, QueryGetTodoRequest, QueryListTodosRequest, MutationCreateTodoResponse, MutationCreateTodoRequest, MutationDeleteTodoRequest] do not exist in the template
UPDATE_ROLLBACK_IN_PROGRESS                  myapp-20180830150843 AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:41 GMT-0500 (CDT) The following resource(s) failed to update: [apimyapp].                                                                                                                                                                                                                                                 
UPDATE_COMPLETE                              apimyapp             AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:45 GMT-0500 (CDT)                                                                                                                                                                                                                                                                                                         
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS myapp-20180830150843 AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:46 GMT-0500 (CDT)                                                                                                                                                                                                                                                                                                         
⠧ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS       apimyapp             AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:47 GMT-0500 (CDT) 
UPDATE_COMPLETE          apimyapp             AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:47 GMT-0500 (CDT) 
UPDATE_ROLLBACK_COMPLETE myapp-20180830150843 AWS::CloudFormation::Stack Fri Aug 31 2018 12:16:48 GMT-0500 (CDT) 
⠦ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

Please advise, I would really like to use this in my current project.

kaustavghosh06 commented 6 years ago

@rygo6 Could you confirm which version of the CLI you’re using? ‘amplify -v’ would give you the version.

kaustavghosh06 commented 6 years ago

@rygo6. Could you tell me how your schem.graphql looks like which is present in amplify/backend/api/myapp/

rygo6 commented 6 years ago

@kaustavghosh06 

ryan@ryan-ubuntu:~/Developer/my-app$ amplify -v
0.1.15

amplify/backend/api/myapp/schema.graphql

type Blog @model {
  id: ID!
  name: String!
  posts: [Post] @connection(name: "BlogPosts")
}

type Post @model {
  id: ID!
  title: String!
  blog: Blog @connection(name: "BlogPosts")
  comments: [Comment] @connection(name: "PostComments")
}

type Comment @model {
  id: ID!
  content: String
  post: Post @connection(name: "PostComments")
}
kaustavghosh06 commented 6 years ago

@rygo6 I was able to reproduce it. So from your amplify/backend/api/myapp/parameters.json file remove all entries except the "AppSyncApiName" key. So your parameters.json should look something like this:

{
    "AppSyncApiName": "myapp"
}

After this do an ampify push. I'm working on a fix for this, but you'll be able to push your graphql API by following the above-mentioned steps in the meanwhile.

kaustavghosh06 commented 6 years ago

This issue should be resolved with the CLI version - 0.1.16.

LeftyTak commented 6 years ago

I'm following this tutorial : https://docs.aws.amazon.com/aws-mobile/latest/developerguide/add-aws-mobile-cloud-logic.html

it failed at the following:

⠙ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack ✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

I've confirmed my CLI version is 1.16.12, and I am still getting the same error. And this thread seems to be the only one addressing the issue. Could someone please post an update? thanks.

HenokT commented 6 years ago

I'm also getting this error when running amplify push after a schema update. I'm using amplify-cli version 0.1.19.

hanming2033 commented 6 years ago

same error with 0.1.22

BAByrne commented 6 years ago

And also with 0.1.23

rypplzzdev commented 6 years ago

same error today with 0.1.18

xaviertorgerson commented 6 years ago

I am having the same error with 0.1.23: Resource is not in the state stackUpdateComplete

Following the GraphQL Transformer Tutorial within an Angular 6 project on OSX 10.13.6 I did the following...

amplify init

amplify add auth
# default auth

amplify add api
? I selected the graphql option.
? When asked for a schema I choose **No**.
? I selected one of the default samples. 
? I choose to edit the schema and it opened the schema.graphql in my editor.
? I made some changes to the schema.
? I saved the file and choose Enter on the command line.
? I am **NOT** asked if I want to use my own Amazon DynamoDB tables
# The last ? Press enter to continue always gets skipped at the end and I cannot prevent it

amplify push
? you want to generate code for your newly created GraphQL API: **Yes**
? Enter the file name pattern of graphql queries, mutations and subscriptions: **src/graphql/**/*.js**
? Choose the code generation language target: **typescript**
? Enter the file name for the generated code: **src/API.ts**
? Do you want to generate/update all possible GraphQL operations - queries, mutations and subscriptions: **Yes**

The logs consist of a lot of creating of resources but I noticed this error: Template error: IAM role driansizzapp-20180924234637-unauthRole doesn't exist I grabbed a few lines before and after. It looks like it begins to DELETE all resources it just created which someone said are still experimental.

CREATE_IN_PROGRESS ListModifierGroupResolver                               AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:23 GMT-0400 (EDT)
CREATE_COMPLETE    ItemGroupmodifiersResolver                              AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:27 GMT-0400 (EDT)
CREATE_COMPLETE    driansizzapp-20180924234637-apimuchogusto-15ULFWUXWKENS AWS::CloudFormation::Stack Tue Sep 25 2018 21:32:30 GMT-0400 (EDT)
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE             apimuchogusto               AWS::CloudFormation::Stack Tue Sep 25 2018 21:32:36 GMT-0400 (EDT)
UPDATE_ROLLBACK_IN_PROGRESS driansizzapp-20180924234637 AWS::CloudFormation::Stack Tue Sep 25 2018 21:32:38 GMT-0400 (EDT) Template error: IAM role driansizzapp-20180924234637-unauthRole doesn't exist
⠦ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS driansizzapp-20180924234637 AWS::CloudFormation::Stack Tue Sep 25 2018 21:32:50 GMT-0400 (EDT)
DELETE_IN_PROGRESS                           apimuchogusto               AWS::CloudFormation::Stack Tue Sep 25 2018 21:32:51 GMT-0400 (EDT)
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS GetModifierGroupResolver                                AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:55 GMT-0400 (EDT)
DELETE_IN_PROGRESS driansizzapp-20180924234637-apimuchogusto-15ULFWUXWKENS AWS::CloudFormation::Stack Tue Sep 25 2018 21:32:52 GMT-0400 (EDT) User Initiated
DELETE_IN_PROGRESS GraphQLAPIKey                                           AWS::AppSync::ApiKey       Tue Sep 25 2018 21:32:55 GMT-0400 (EDT)
DELETE_COMPLETE    ModifierGroupitemGroupResolver                          AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:57 GMT-0400 (EDT)
DELETE_COMPLETE    DeleteModifierResolver                                  AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:57 GMT-0400 (EDT)
DELETE_COMPLETE    ItemitemGroupResolver                                   AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:57 GMT-0400 (EDT)
DELETE_COMPLETE    ItemGroupitemsResolver                                  AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:56 GMT-0400 (EDT)
DELETE_COMPLETE    DeleteItemResolver                                      AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:56 GMT-0400 (EDT)
DELETE_COMPLETE    GetModifierGroupResolver                                AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:56 GMT-0400 (EDT)
DELETE_COMPLETE    ListModifierResolver                                    AWS::AppSync::Resolver     Tue Sep 25 2018 21:32:56 GMT-0400 (EDT)

It ends with the following...

DELETE_COMPLETE          authcognito0d92e4b9         AWS::CloudFormation::Stack Tue Sep 25 2018 21:35:02 GMT-0400 (EDT)
UPDATE_ROLLBACK_COMPLETE driansizzapp-20180924234637 AWS::CloudFormation::Stack Tue Sep 25 2018 21:35:03 GMT-0400 (EDT)
⠼ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
kaustavghosh06 commented 6 years ago

Would be great if everyone could provide a screenshot of the logs or just paste the logs out here for us to narrow down the issue - along with the OS used.

ncirkel commented 6 years ago

For me this happens when pushing the same project first from the Linux subsystem in Windows (using Ubuntu), and then from a new Ubuntu 18.04.1 install. I don't know if that's related. Amplify version is 0.1.26.

I tried removing everything except AppSyncApiName from amplify/backend/api/myapp/parameters.json, that didn't help.

Here are the logs:

amplify push
| Category | Resource name   | Operation | Provider plugin   |
| -------- | --------------- | --------- | ----------------- |
| Api      | xxxxxxxxxxxxx   | Update    | awscloudformation |
| Auth     | yyyyyyyyyyyyyyy | No Change | awscloudformation |
? Are you sure you want to continue? true
? Do you want to update code for your updated GraphQL API (Y/n)
? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types? This will overwrite your current graphql queries, mutations and subscriptions (Y/n)
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types? This will overwrite your current graphql queries, mutations and subscriptions Yes
⠴ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          xxxxxxxxxxxxx-20180922180831 AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:30 GMT+0200 (CEST) User Initiated
UPDATE_IN_PROGRESS          authyyyyyyyyyyyyyyy          AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:33 GMT+0200 (CEST)
UPDATE_IN_PROGRESS          apixxxxxxxxxxxxx             AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:33 GMT+0200 (CEST)
UPDATE_FAILED               authyyyyyyyyyyyyyyy          AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:34 GMT+0200 (CEST) Parameters: [authRoleArn, autoVerifiedAttributes, allowUnauthenticatedIdentities, smsVerificationMessage, userpoolClientReadAttributes, mfaTypes, emailVerificationSubject, useDefault, openIdLambdaIAMPolicy, userpoolClientGenerateSecret, mfaConfiguration, userpoolClientLogPolicy, openIdRolePolicy, identityPoolName, openIdLogPolicy, thirdPartyAuth, authSelections, smsAuthenticationMessage, roleExternalId, mfaLambdaLogPolicy, passwordPolicyMinLength, userPoolName,openIdLambdaRoleName, policyName, userpoolClientName, userpoolClientLambdaPolicy, resourceName, mfaLambdaIAMPolicy, mfaPassRolePolicy, emailVerificationMessage, userpoolClientRefreshTokenValidity,userpoolClientSetAttributes, unAuthRoleName, authRoleName, requiredAttributes, roleName, passwordPolicyCharacters, lambdaLogPolicy, unAuthRoleArn, userpoolClientLambdaRole, defaultPasswordPolicy, mfaLambdaRole] must have values
UPDATE_FAILED               apixxxxxxxxxxxxx             AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:34 GMT+0200 (CEST) Parameters: [ResolverBucket, ResolverRootKey, DeploymentTimestamp, schemaGraphql] must have values
UPDATE_ROLLBACK_IN_PROGRESS xxxxxxxxxxxxx-20180922180831 AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:35 GMT+0200 (CEST) The following resource(s) failed to update: [apixxxxxxxxxxxxx, authyyyyyyyyyyyyyyy].
UPDATE_COMPLETE             authyyyyyyyyyyyyyyy          AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:39 GMT+0200 (CEST)
UPDATE_COMPLETE             apixxxxxxxxxxxxx             AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:39 GMT+0200 (CEST)
⠧ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS xxxxxxxxxxxxx-20180922180831 AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:40 GMT+0200 (CEST)
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS       apixxxxxxxxxxxxx             AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:41 GMT+0200 (CEST)
UPDATE_COMPLETE          apixxxxxxxxxxxxx             AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:42 GMT+0200 (CEST)
UPDATE_IN_PROGRESS       authyyyyyyyyyyyyyyy          AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:43 GMT+0200 (CEST)
UPDATE_COMPLETE          authyyyyyyyyyyyyyyy          AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:43 GMT+0200 (CEST)
UPDATE_ROLLBACK_COMPLETE xxxxxxxxxxxxx-20180922180831 AWS::CloudFormation::Stack Tue Oct 02 2018 10:18:43 GMT+0200 (CEST)
⠴ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
usulix commented 6 years ago

I got this error when trying to add auth with a Google web app ID. I think the ID Google gave me exceeded the constraints 

failed to satisfy constraint: Map value must satisfy constraint: [Member must have length less than or equal to 128, Member must have length greater than or equal to 1, Member must satisfy regular expression pattern: [\w.;_/-]+] (Service: AmazonCognitoIdentity; Status Code: 400; Error Code: ValidationException; Request ID: 4f34a3e6-cc2b-11e8-afe5-af342c13d093)

skipped the 3rd party Auth and push succeeded

stefsietz commented 6 years ago

same problem for me, lots of CREATE_FAILED logs, "Resource is not in the state stackUpdateComplete" at the end. Ubuntu 18.04, cli 0.1.27

Edit: oh and I got this by stricly following the setup instructions here: https://github.com/aws-samples/aws-amplify-vue

budkin76 commented 6 years ago

I ran amplify delete, then tried to start over and now I get this error after adding auth and pushing it.

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

budkin76 commented 6 years ago

FYI the only way I could get rid of this message was to delete aws-amplify from my project then delete the global npm package @aws-amplify/cli. I then reinstalled @aws-amplify/cli, ran amplify configure, then amplify init in my project. Once I added auth I was able to push it again.

mdahlke commented 6 years ago

Having the same issue. Here are my logs:

$ amplify push
| Category | Resource name   | Operation | Provider plugin   |
| -------- | --------------- | --------- | ----------------- |
| Api      | XXXXXXXXXXXX    | Update    | awscloudformation |
| Auth     | XXXXXXXXXXXX    | No Change | awscloudformation |
| Storage  | XXXXXXXXXXXX    | No Change | awscloudformation |
? Are you sure you want to continue? true

GraphQL schema compiled successfully. Edit your schema at /Users/mdahlke/Sites/websites/amplify/vue-sample-app/app/amplify/backend/api/vuesampleapp/schema.graphql
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          XXXXXXXXXXXX AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:00 GMT-0500 (Central Daylight Time) User Initiated                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            
UPDATE_IN_PROGRESS          storageXXXXXXX           AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:04 GMT-0500 (Central Daylight Time)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           
UPDATE_FAILED               storageXXXXXXX           AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:05 GMT-0500 (Central Daylight Time) Parameters: [bucketName, unauthPolicyName, authRoleName, unauthRoleName, unauthPermissions, authPolicyName, authPermissions] must have values                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             
UPDATE_IN_PROGRESS          authXXXXXXX         AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:05 GMT-0500 (Central Daylight Time)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           
UPDATE_FAILED               authXXXXXXX         AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:05 GMT-0500 (Central Daylight Time) Parameters: [authRoleArn, autoVerifiedAttributes, allowUnauthenticatedIdentities, smsVerificationMessage, userpoolClientReadAttributes, mfaTypes, emailVerificationSubject, useDefault, openIdLambdaIAMPolicy, userpoolClientGenerateSecret, mfaConfiguration, userpoolClientLogPolicy, openIdRolePolicy, identityPoolName, openIdLogPolicy, thirdPartyAuth, authSelections, smsAuthenticationMessage, roleExternalId, mfaLambdaLogPolicy, passwordPolicyMinLength, userPoolName, openIdLambdaRoleName, policyName, userpoolClientName, userpoolClientLambdaPolicy, resourceName, mfaLambdaIAMPolicy, mfaPassRolePolicy, emailVerificationMessage, userpoolClientRefreshTokenValidity, userpoolClientSetAttributes, unAuthRoleName, authRoleName, requiredAttributes, roleName, passwordPolicyCharacters, lambdaLogPolicy, unAuthRoleArn, userpoolClientLambdaRole, defaultPasswordPolicy, mfaLambdaRole] must have values
UPDATE_ROLLBACK_IN_PROGRESS XXXXXXXXXXXX AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:06 GMT-0500 (Central Daylight Time) The following resource(s) failed to update: [storageXXXXXXX, authXXXXXXX].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              storageXXXXXXX           AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:11 GMT-0500 (Central Daylight Time) 
UPDATE_COMPLETE                              authXXXXXXX         AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:11 GMT-0500 (Central Daylight Time) 
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS XXXXXXXXXXXX AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:12 GMT-0500 (Central Daylight Time) 
UPDATE_IN_PROGRESS                           storageXXXXXXX           AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:13 GMT-0500 (Central Daylight Time) 
UPDATE_IN_PROGRESS                           authXXXXXXX         AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:13 GMT-0500 (Central Daylight Time) 
UPDATE_COMPLETE                              storageXXXXXXX           AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:13 GMT-0500 (Central Daylight Time) 
UPDATE_COMPLETE                              authXXXXXXX         AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:13 GMT-0500 (Central Daylight Time) 
UPDATE_ROLLBACK_COMPLETE                     XXXXXXXXXXXX AWS::CloudFormation::Stack Sun Oct 14 2018 16:24:14 GMT-0500 (Central Daylight Time) 
⠼ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
tenerifeonline commented 6 years ago

Same issue here. Log looks as follows. Please advise, this issue is blocking my project ...

Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS tenerifeonlineadmin-20181014173936 AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:19 GMT+0100 (WEST) User Initiated
UPDATE_IN_PROGRESS authcognitoedc34406                AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:23 GMT+0100 (WEST)
UPDATE_COMPLETE    authcognitoedc34406                AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:23 GMT+0100 (WEST)
UPDATE_IN_PROGRESS apitenerifeonlineadmin             AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:26 GMT+0100 (WEST)
⠏ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS tenerifeonlineadmin-20181014173936-apitenerifeonlineadmin-Q0QKXOMB1VRO AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:26 GMT+0100 (WEST) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          PropertyTable                                                          AWS::DynamoDB::Table        Tue Oct 16 2018 19:13:34 GMT+0100 (WEST)
UPDATE_IN_PROGRESS          GraphQLSchema                                                          AWS::AppSync::GraphQLSchema Tue Oct 16 2018 19:13:34 GMT+0100 (WEST)
UPDATE_IN_PROGRESS          ImgTable                                                               AWS::DynamoDB::Table        Tue Oct 16 2018 19:13:34 GMT+0100 (WEST)
UPDATE_FAILED               PropertyTable                                                          AWS::DynamoDB::Table        Tue Oct 16 2018 19:13:34 GMT+0100 (WEST) Attempting to create an index which already exists (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: R8CFAE5RLQVHLQIDI03E57JGCJVV4KQNSO5AEMVJF66Q9ASUAAJG)
UPDATE_FAILED               ImgTable                                                               AWS::DynamoDB::Table        Tue Oct 16 2018 19:13:34 GMT+0100 (WEST) Cannot perform more than one GSI creation or deletion in a single update
UPDATE_FAILED               GraphQLSchema                                                          AWS::AppSync::GraphQLSchema Tue Oct 16 2018 19:13:35 GMT+0100 (WEST) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS tenerifeonlineadmin-20181014173936-apitenerifeonlineadmin-Q0QKXOMB1VRO AWS::CloudFormation::Stack  Tue Oct 16 2018 19:13:36 GMT+0100 (WEST) The following resource(s) failed to update: [ImgTable, GraphQLSchema, PropertyTable].
UPDATE_FAILED               apitenerifeonlineadmin                                                 AWS::CloudFormation::Stack  Tue Oct 16 2018 19:13:37 GMT+0100 (WEST) Embedded stack arn:aws:cloudformation:eu-central-1:645867932780:stack/tenerifeonlineadmin-20181014173936-apitenerifeonlineadmin-Q0QKXOMB1VRO/2b0a38a0-d127-11e8-919d-503f2ad2e59a was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESSwith reason: The following resource(s) failed to update: [ImgTable, GraphQLSchema, PropertyTable].
UPDATE_ROLLBACK_IN_PROGRESS tenerifeonlineadmin-20181014173936                                     AWS::CloudFormation::Stack  Tue Oct 16 2018 19:13:38 GMT+0100 (WEST) The following resource(s) failed to update: [apitenerifeonlineadmin].
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS authcognitoedc34406    AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:46 GMT+0100 (WEST)
UPDATE_COMPLETE    authcognitoedc34406    AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:47 GMT+0100 (WEST)
UPDATE_IN_PROGRESS apitenerifeonlineadmin AWS::CloudFormation::Stack Tue Oct 16 2018 19:13:48 GMT+0100 (WEST)
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE PropertyTable AWS::DynamoDB::Table        Tue Oct 16 2018 19:14:08 GMT+0100 (WEST)
UPDATE_COMPLETE GraphQLSchema AWS::AppSync::GraphQLSchema Tue Oct 16 2018 19:14:08 GMT+0100 (WEST)
UPDATE_COMPLETE ImgTable      AWS::DynamoDB::Table        Tue Oct 16 2018 19:14:08 GMT+0100 (WEST)
⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS tenerifeonlineadmin-20181014173936-apitenerifeonlineadmin-Q0QKXOMB1VRO AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:12 GMT+0100 (WEST)
⠴ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              apitenerifeonlineadmin                                                 AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:22 GMT+0100 (WEST)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS tenerifeonlineadmin-20181014173936                                     AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:23 GMT+0100 (WEST)
UPDATE_IN_PROGRESS                           apitenerifeonlineadmin                                                 AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:24 GMT+0100 (WEST)
UPDATE_ROLLBACK_COMPLETE                     tenerifeonlineadmin-20181014173936-apitenerifeonlineadmin-Q0QKXOMB1VRO AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:25 GMT+0100 (WEST)
⠋ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE          apitenerifeonlineadmin             AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:35 GMT+0100 (WEST)
UPDATE_IN_PROGRESS       authcognitoedc34406                AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:36 GMT+0100 (WEST)
UPDATE_COMPLETE          authcognitoedc34406                AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:36 GMT+0100 (WEST)
UPDATE_ROLLBACK_COMPLETE tenerifeonlineadmin-20181014173936 AWS::CloudFormation::Stack Tue Oct 16 2018 19:14:36 GMT+0100 (WEST)
⠹ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
michaelcaterisano commented 6 years ago

I've been having the same issue. It seems in my case that changing the schema definition fixed the problem. This did not work: 

type Product @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String!
  price: Float!
  vendor: String
  category: String
  units: String
  defaultqty: Int
  maxqty: Int
}

type Order @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  products: [Product!]!
}

But this did (added name field to the Order type):

type Product @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String!
  price: Float!
  vendor: String
  category: String
  units: String
  defaultqty: Int
  maxqty: Int
}

type Order @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String
  products: [Product!]!
}

Any ideas why?

kaustavghosh06 commented 6 years ago

@mdahlke Can you run amplify update auth -> Yes, use default configurations and then amplify push? That should hopefully resolve your issue.

kaustavghosh06 commented 6 years ago

@tenerifeonline can I take a look at your schema?

kavaro commented 6 years ago

@kaustavghosh06, @tenerifeonline asked me to let you know that due to project pressure he was forced back to firestore for the current project. He will be watching amplify-cli closely going forward and plans to use it in a future project as it looks extremely promising, keep up the good work. Unfortunately, he lost his graphql schema because the "amplify delete" command removed the schema file and he has currently no time to recreate that file. P.S. It would be great if "amplify delete" would not automatically delete the schema and leave the graphql schema file in the amplify directory.

mikeparisstuff commented 6 years ago

@michaelcaterisano The issue is that when trying to generate the CreateOrderInput type, there are no valid fields because "id" is stripped away as it is generated on the server and the connection field will not generate a field either. Adding the scalar field makes it work because it has a valid input field again. The fix is to add a check here (https://github.com/aws-amplify/amplify-cli/blob/master/packages/graphql-dynamodb-transformer/src/DynamoDBModelTransformer.ts#L145) that makes sure each input types has at least one field and if it does not, do not generate that input type or the corresponding mutation field.

This will be fixed as soon as I can get to it which should be in the next few days.

michaelcaterisano commented 6 years ago

Got it, that makes sense. Thanks @mikeparisstuff!

michaelcaterisano commented 6 years ago

Now trying the following schema and getting the same error. Will post the stack trace also. Consistently seeing "Cannot perform more than one GSI creation or deletion in a single update" in the trace.

type Vendor @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String!
}

type Product @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String!
  price: Float!
  vendor: Vendor @connection
  category: String
  units: String
  defaultqty: Int
  maxqty: Int
}

type Order @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String
  products: [Product]
}

And stack trace. 

UPDATE_IN_PROGRESS tampoporeactamplify-20181018104010 AWS::CloudFormation::Stack Tue Oct23 2018 00:42:12 GMT-0400 (Eastern Daylight Time) User Initiated
UPDATE_IN_PROGRESS authcognito2f0d4060                AWS::CloudFormation::Stack Tue Oct23 2018 00:42:16 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS hostingS3AndCloudFront             AWS::CloudFormation::Stack Tue Oct23 2018 00:42:16 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    authcognito2f0d4060                AWS::CloudFormation::Stack Tue Oct23 2018 00:42:17 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    hostingS3AndCloudFront             AWS::CloudFormation::Stack Tue Oct23 2018 00:42:17 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS apitampopoapi                      AWS::CloudFormation::Stack Tue Oct23 2018 00:42:19 GMT-0400 (Eastern Daylight Time)
⠋ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:20 GMT-0400 (Eastern Daylight Time) User Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          GraphQLSchema  AWS::AppSync::GraphQLSchema Tue Oct 23 2018 00:42:28 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS          ProductTable  AWS::DynamoDB::Table        Tue Oct 23 2018 00:42:28 GMT-0400 (Eastern Daylight Time)
UPDATE_FAILED               ProductTable  AWS::DynamoDB::Table        Tue Oct 23 2018 00:42:28 GMT-0400 (Eastern Daylight Time) Cannot perform more than one GSI creation or deletion in a single update
UPDATE_FAILED               GraphQLSchema  AWS::AppSync::GraphQLSchema Tue Oct 23 2018 00:42:29 GMT-0400 (Eastern Daylight Time) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack  Tue Oct 23 2018 00:42:30 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to update: [ProductTable, GraphQLSchema].
UPDATE_FAILED               apitampopoapi  AWS::CloudFormation::Stack  Tue Oct 23 2018 00:42:31 GMT-0400 (Eastern Daylight Time) Embedded stack arn:aws:cloudformation:us-east-1:175773093744:stack/tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH/4cd15b60-d2e6-11e8-85d3-50faeaee4499 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [ProductTable, GraphQLSchema].
UPDATE_ROLLBACK_IN_PROGRESS tampoporeactamplify-20181018104010  AWS::CloudFormation::Stack  Tue Oct 23 2018 00:42:32 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to update: [apitampopoapi].
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS hostingS3AndCloudFront AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:43 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS authcognito2f0d4060    AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:44 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    hostingS3AndCloudFront AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:44 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    authcognito2f0d4060    AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:44 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS apitampopoapi          AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:45 GMT-0400 (Eastern Daylight Time)
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ProductTable                   AWS::DynamoDB::Table        Tue Oct 23 2018 00:43:13 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              GraphQLSchema                   AWS::AppSync::GraphQLSchema Tue Oct 23 2018 00:43:14 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:19 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              apitampopoapi                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:20 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS tampoporeactamplify-20181018104010                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:20 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS                           apitampopoapi                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:22 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS                           hostingS3AndCloudFront                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:22 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              hostingS3AndCloudFront                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:22 GMT-0400 (Eastern Daylight Time)
⠋ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:23 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE          apitampopoapi                                                  AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:32 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS       authcognito2f0d4060                                            AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:33 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE          authcognito2f0d4060                                            AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:34 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE tampoporeactamplify-20181018104010                             AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:34 GMT-0400 (Eastern Daylight Time)
⠇ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
michaelcaterisano commented 6 years ago

I think I may have realized the issue. Once I add a @connection directive, it seems that it's not possible to remove it and then amplify push again. This seems to be because adding a @connection adds a GSI, which seems impossible to remove after adding. Is there a workaround for this? So far I've just had to amplify delete and start over when making changes to @connection directives.

mikeparisstuff commented 5 years ago

@michaelcaterisano How many [pairs of] @connection fields were you tweaking in the single update? I believe the issue only occurs when making changes that result in more than 1 GSI create/update/delete on a single table. In the short term, you can get around this issue by breaking up the push into multiple steps where you only change 1 connection at a time. In the long term, I think we can get around these issues with tooling that warns you or, even better, that automatically breaks up the push into multiple steps. I will also take an action item to document this in the amplify docs.

E.G. The CLI works when going from:

type Meeting @model {
  id: ID!
  name: String!
  room: Room @connection(name: "RoomMeetings")
}

type Room @model {
  id: ID!
  number: Int!
  meetings: [Meeting] @connection(name: "RoomMeetings")
}

to:

type Meeting @model {
  id: ID!
  name: String!
}

type Room @model {
  id: ID!
  number: Int!
}

It also works when going from:

type Meeting @model {
  id: ID!
  name: String!
  room: Room @connection
}

to:

type Meeting @model {
  id: ID!
  name: String!
}

I noticed that it does fail when trying to add multiple connections to a model type in a single push and the reason is that DynamoDB has a limit on the number of GSIs on a single table that you can touch in a single CloudFormation update stack invocation.

E.G. When trying to go from:

type Meeting @model {
  id: ID!
  name: String!
}

type Room @model {
  id: ID!
  number: Int!
}

to:

type Meeting @model {
  id: ID!
  name: String!

  # Both of these connections will try to create GSIs on the Meeting table.
  room: Room @connection(name: "RoomMeetings")
  backupRoom: Room @connection(name: "BackupMeetings")
}

type Room @model {
  id: ID!
  number: Int!

  # Uses the same two GSIs on the Meeting table.
  meetings: [Meeting] @connection(name: "RoomMeetings")
  backupMeetings: [Meeting] @connection(name: "BackupMeetings")
}

will fail with the error

Cannot perform more than one GSI creation or deletion in a single update

We are working on bypassing a number of CloudFormation & other service related limits but for now, you can sidestep this issue by breaking your update into multiple steps. For example, we can get the above schema to work by first going from:

type Meeting @model {
  id: ID!
  name: String!
}

type Room @model {
  id: ID!
  number: Int!
}

to:

type Meeting @model {
  id: ID!
  name: String!
  room: Room @connection(name: "RoomMeetings")
}

type Room @model {
  id: ID!
  number: Int!
  meetings: [Meeting] @connection(name: "RoomMeetings")
}

and then to:

type Meeting @model {
  id: ID!
  name: String!
  room: Room @connection(name: "RoomMeetings")
  backupRoom: Room @connection(name: "BackupMeetings")
}

type Room @model {
  id: ID!
  number: Int!
  meetings: [Meeting] @connection(name: "RoomMeetings")
  backupMeetings: [Meeting] @connection(name: "BackupMeetings")
}
michaelcaterisano commented 5 years ago

Excellent, thanks!

rcwestlake commented 5 years ago

@mikeparisstuff thx for the update. I made some material changes to my schema (removed several connection references) and adding them back and then making several updates doesn't seem practical because I've made other code changes based on the new schema changes. When I went into my S3 bucket and it seemed stuff has updated (updatedAt time changed). Am I stuck until your fix comes in? Best to just delete and re-start?

Also, I'm still trying to figure out how to keep my local resources in sync with changes made in the console. For example, my schema.graphql is different in local amplify/backend/api/<apiname>/schema.graphql and the version in the AWS console. How do I update the local to keep them in sync so when I push it doesn't overwrite my changes? When I update the files in amplify/backend/api/<apiname>/build/schema.graphql it gets overridden when I do amplify push.

pechisworks commented 5 years ago

I've to solve the issue like @mikeparisstuff mentioned, but this didn't worked for me. What solved my Problem was to reset the "Read/write capacity mode" back to "On-demand", then amplify push worked.

grigorebudac commented 5 years ago

I have faced the same issue and it was caused by changing the project's route or name. To solve it open amplify/.config/project-config.json and check projectPath

NurdinDev commented 5 years ago

Possibly caused by use of experimental amplify delete feature in project directory prior to re-running amplify init.

@haverchuck If we face like this issue in production, amplify delete will delete all tables and data, right ? so what is safer way to use delete in production ?

dipjyotimetia commented 5 years ago

Please install npm i -g @aws-amplify/cli and you will not have any issue

dipjyotimetia commented 5 years ago

I have this issue too.

my log

ryan@ryan-ubuntu:~/Developer/myappclone$ amplify push
| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | myapp         | Update    | awscloudformation |
? Are you sure you want to continue? true
⠋ Updating resources in the cloud. This may take a few minutes...
GraphQL schema compiled successfully. Edit your schema at /home/ryan/Developer/myappclone/amplify/backend/api/myapp/schema.graphql
⠦ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:36 GMT-0500 (CDT) User Initiated                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      
UPDATE_IN_PROGRESS          apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:40 GMT-0500 (CDT)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     
UPDATE_FAILED               apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:40 GMT-0500 (CDT) Parameters: [MutationDeletePostResponse, MutationDeleteBlogResponse, QueryListCommentsResponse, MutationDeleteBlogRequest, MutationUpdateCommentRequest, PostBlogResponse, MutationCreatePostRequest, QueryGetCommentRequest, MutationUpdatePostRequest, MutationDeleteCommentRequest, CommentPostRequest, QueryListBlogsResponse, MutationUpdateCommentResponse, PostCommentsResponse, MutationCreatePostResponse, QueryGetBlogResponse, MutationCreateBlogResponse, QueryGetPostResponse, MutationCreateCommentRequest, CommentPostResponse, MutationUpdatePostResponse, QueryGetCommentResponse, MutationUpdateBlogResponse, MutationDeletePostRequest, QueryGetBlogRequest, QueryListPostsResponse, QueryListCommentsRequest, BlogPostsResponse, MutationCreateBlogRequest, BlogPostsRequest, QueryGetPostRequest, MutationUpdateBlogRequest, PostBlogRequest, MutationCreateCommentResponse, QueryListPostsRequest, QueryListBlogsRequest, MutationDeleteCommentResponse, PostCommentsRequest] must have values
UPDATE_ROLLBACK_IN_PROGRESS myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:41 GMT-0500 (CDT) The following resource(s) failed to update: [apimyapp].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             
⠙ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:50 GMT-0500 (CDT) 
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:50 GMT-0500 (CDT) 
UPDATE_IN_PROGRESS                           apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:51 GMT-0500 (CDT) 
UPDATE_COMPLETE                              apimyapp             AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:52 GMT-0500 (CDT) 
UPDATE_ROLLBACK_COMPLETE                     myapp-20180830150843 AWS::CloudFormation::Stack Thu Aug 30 2018 16:35:52 GMT-0500 (CDT) 
⠧ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

Please install npm i -g @aws-amplify/cli and you will not have any issue

dipjyotimetia commented 5 years ago

Now trying the following schema and getting the same error. Will post the stack trace also. Consistently seeing "Cannot perform more than one GSI creation or deletion in a single update" in the trace.

type Vendor @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String!
}

type Product @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String!
  price: Float!
  vendor: Vendor @connection
  category: String
  units: String
  defaultqty: Int
  maxqty: Int
}

type Order @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  name: String
  products: [Product]
}

And stack trace.

UPDATE_IN_PROGRESS tampoporeactamplify-20181018104010 AWS::CloudFormation::Stack Tue Oct23 2018 00:42:12 GMT-0400 (Eastern Daylight Time) User Initiated
UPDATE_IN_PROGRESS authcognito2f0d4060                AWS::CloudFormation::Stack Tue Oct23 2018 00:42:16 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS hostingS3AndCloudFront             AWS::CloudFormation::Stack Tue Oct23 2018 00:42:16 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    authcognito2f0d4060                AWS::CloudFormation::Stack Tue Oct23 2018 00:42:17 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    hostingS3AndCloudFront             AWS::CloudFormation::Stack Tue Oct23 2018 00:42:17 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS apitampopoapi                      AWS::CloudFormation::Stack Tue Oct23 2018 00:42:19 GMT-0400 (Eastern Daylight Time)
⠋ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:20 GMT-0400 (Eastern Daylight Time) User Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          GraphQLSchema  AWS::AppSync::GraphQLSchema Tue Oct 23 2018 00:42:28 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS          ProductTable  AWS::DynamoDB::Table        Tue Oct 23 2018 00:42:28 GMT-0400 (Eastern Daylight Time)
UPDATE_FAILED               ProductTable  AWS::DynamoDB::Table        Tue Oct 23 2018 00:42:28 GMT-0400 (Eastern Daylight Time) Cannot perform more than one GSI creation or deletion in a single update
UPDATE_FAILED               GraphQLSchema  AWS::AppSync::GraphQLSchema Tue Oct 23 2018 00:42:29 GMT-0400 (Eastern Daylight Time) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack  Tue Oct 23 2018 00:42:30 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to update: [ProductTable, GraphQLSchema].
UPDATE_FAILED               apitampopoapi  AWS::CloudFormation::Stack  Tue Oct 23 2018 00:42:31 GMT-0400 (Eastern Daylight Time) Embedded stack arn:aws:cloudformation:us-east-1:175773093744:stack/tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH/4cd15b60-d2e6-11e8-85d3-50faeaee4499 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [ProductTable, GraphQLSchema].
UPDATE_ROLLBACK_IN_PROGRESS tampoporeactamplify-20181018104010  AWS::CloudFormation::Stack  Tue Oct 23 2018 00:42:32 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to update: [apitampopoapi].
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS hostingS3AndCloudFront AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:43 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS authcognito2f0d4060    AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:44 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    hostingS3AndCloudFront AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:44 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    authcognito2f0d4060    AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:44 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS apitampopoapi          AWS::CloudFormation::Stack Tue Oct 23 2018 00:42:45 GMT-0400 (Eastern Daylight Time)
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ProductTable                   AWS::DynamoDB::Table        Tue Oct 23 2018 00:43:13 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              GraphQLSchema                   AWS::AppSync::GraphQLSchema Tue Oct 23 2018 00:43:14 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:19 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              apitampopoapi                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:20 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS tampoporeactamplify-20181018104010                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:20 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS                           apitampopoapi                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:22 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS                           hostingS3AndCloudFront                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:22 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              hostingS3AndCloudFront                   AWS::CloudFormation::Stack  Tue Oct 23 2018 00:43:22 GMT-0400 (Eastern Daylight Time)
⠋ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE tampoporeactamplify-20181018104010-apitampopoapi-1VC62R58TY2UH AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:23 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE          apitampopoapi                                                  AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:32 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS       authcognito2f0d4060                                            AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:33 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE          authcognito2f0d4060                                            AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:34 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE tampoporeactamplify-20181018104010                             AWS::CloudFormation::Stack Tue Oct 23 2018 00:43:34 GMT-0400 (Eastern Daylight Time)
⠇ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

Please install npm i -g @aws-amplify/cli and you will not have any issue

iqdev-ca commented 5 years ago

like @dipjyotimetia suggested npm i -g @aws-amplify/cli worked. But after I also did:

amplify remove auth Followed by

amplify add auth Then amplify push didn't give any errors.

UpToEleven1102 commented 5 years ago 
UPDATE_COMPLETE    storagehdtvstorage       AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:22 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE    functionStripeProductsFn AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE    analyticshdtvanalytics   AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS storagehdtvstorage       AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time)
UPDATE_FAILED      authhdtvauth             AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time) Parameters: [resourceNameTruncated, dependsOn] must have values
UPDATE_IN_PROGRESS functionStripeProductsFn AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS analyticshdtvanalytics   AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS authhdtvauth             AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:21 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS hdtv-prod-20190706213816 AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:17 GMT-0500 (Central Daylight Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_IN_PROGRESS hdtv-prod-20190706213816 AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:22 GMT-0500 (Central Daylight Time) The following resource(s) failed to update: [authhdtvauth].
⠧ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE    storagehdtvstorage       AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:31 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE    analyticshdtvanalytics   AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:31 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE    functionStripeProductsFn AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:30 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS storagehdtvstorage       AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:30 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS analyticshdtvanalytics   AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:30 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE    authhdtvauth             AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:30 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS functionStripeProductsFn AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:30 GMT-0500 (Central Daylight Time)
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS hdtv-prod-20190706213816 AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:32 GMT-0500 (Central Daylight Time)
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE hdtv-prod-20190706213816 AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:34 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE          functionStripeProductsFn AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:34 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE          storagehdtvstorage       AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:34 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE          authhdtvauth             AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:34 GMT-0500 (Central Daylight Time)
UPDATE_COMPLETE          analyticshdtvanalytics   AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:34 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       functionStripeProductsFn AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:33 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       storagehdtvstorage       AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:33 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       analyticshdtvanalytics   AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:33 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       authhdtvauth             AWS::CloudFormation::Stack Fri Oct 11 2019 15:39:33 GMT-0500 (Central Daylight Time)
⠴ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack

Following resources failed

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occured during the push operation: Resource is not in the state stackUpdateComplete

I have been stuck here for couple of days and could not move on with my project due to this error. Any idea how to solve it?

patrickridd commented 5 years ago

I solved the issue by following @iqdev-ca and @dipjyotimetia , but after installing aws-amplify/cli I deleted amplify from my directory and reinitialized. These were the exact steps

I ran the command that @dipjyotimetia suggested:

npm i -g @aws-amplify/cli

I then deleted amplify by:

amplify delete

I then initialized amplify, added auth, and pushed:

amplify init amplify add auth amplify push

This finally solved the issue!!

UpToEleven1102 commented 5 years ago

image My problem is that currently I have Comment and VideoComment models; both are in same Comment stack. Now, every time I modify the schema and do amplify push, amplify attempts to create VideoComment stack separately with DynamoDB table; while in fact, VideoComment table is already exists. That just messes everything up. I'm stuck with this for like 2 weeks now. It would be easy to do amplify something remove and amplify something add again but this happens on my Production Env. Any idea how to solve this?

Update: kinda don't want to create and modify stack template manually.

YahngSungho commented 4 years ago

@patrickridd

I solved the issue by following @iqdev-ca and @dipjyotimetia , but after installing aws-amplify/cli I deleted amplify from my directory and reinitialized. These were the exact steps

I ran the command that @dipjyotimetia suggested:

npm i -g @aws-amplify/cli

I then deleted amplify by:

amplify delete

I then initialized amplify, added auth, and pushed:

amplify init amplify add auth amplify push

This finally solved the issue!!

I've tried this and it worked one time, but after a while it became not to work. I don't know what condition makes it not to work. But it's unreasonable to delete everytime when this error occurs. And this error continuously occurs.

martaGonz commented 4 years ago

@patrickridd

I solved the issue by following @iqdev-ca and @dipjyotimetia , but after installing aws-amplify/cli I deleted amplify from my directory and reinitialized. These were the exact steps I ran the command that @dipjyotimetia suggested: npm i -g @aws-amplify/cli I then deleted amplify by: amplify delete I then initialized amplify, added auth, and pushed: amplify init amplify add auth amplify push This finally solved the issue!!

I've tried this and it worked one time, but after a while it became not to work. I don't know what condition makes it not to work. But it's unreasonable to delete everytime when this error occurs. And this error continuously occurs.

this happens to me too. I had to delete all my environment to solve this issue and I am again unable to do 'amplify push' and delete an auth

Template error: instance of Fn::GetAtt references undefined resource authyoaAuth An error occured during the push operation: Template error: instance of Fn::GetAtt references undefined resource authyoaAuth

Alex-Mann commented 4 years ago

Got the same issue here... anyway we can update the error messages to make them more useful?

jarrettj commented 4 years ago

Is it not just a case of manually deleting the current GSI and creating the one that you want manually? Will give that a try. As I'm working on a live system. Will backup table of cheese :).

fireflysemantics commented 4 years ago

Follow these reset instructions: https://medium.com/@ole.ersoy/resetting-aws-amplify-22fff655f2e2

rnagasamy commented 4 years ago

like @dipjyotimetia suggested npm i -g @aws-amplify/cli worked. But after I also did:

amplify remove auth Followed by

amplify add auth Then amplify push didn't give any errors.

TThis doesnt work.

ghost commented 4 years ago

like @dipjyotimetia suggested npm i -g @aws-amplify/cli worked. But after I also did: amplify remove auth Followed by amplify add auth Then amplify push didn't give any errors.

TThis doesnt work.

same here, added auth and pushed