AWS Auth 更新失败卡在 UPDATE_ROLLBACK_FAILED 状态
AWS Auth update failed stuck on UPDATE_ROLLBACK_FAILED state
我已将 google 登录添加到我的应用程序并尝试推送修改，但我没有这样做的权限。获得权限后，我尝试放大推送但出现此错误：
Stack:arn:aws:cloudformation:us-east-1:432853258441:stack/amplify-huruproject-local-190356/117b7360-c94d-11eb-a4cc-0e8a861a6983 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
推送操作发生错误：Stack:arn:aws:cloudformation:us-east-1:432853258441:stack/amplify-huruproject-local-190356/117b7360-c94d-11eb-a4cc-0e8a861a6983处于UPDATE_ROLLBACK_FAILED状态，无法更新。
问题是我在我的堆栈控制台中找不到这个特定的堆栈。我怎样才能解决这个问题？
更新：
我找到了堆栈，它在一个自动生成的嵌套堆栈中。
这是我发现的：
我不知道如何从这里开始。我应该删除整个堆栈吗？我会丢失所有数据吗？
根据 documentation，您可以删除堆栈或尝试继续回滚。最简单的解决方案是删除堆栈并重试。
摘要如下：
If your stack is stuck in the UPDATE_ROLLBACK_FAILED state after a failed update, then the only actions that you can perform on the stack are the ContinueUpdateRollback or DeleteStack operations. This is because CloudFormation requires further input from you to acknowledge that the stack is out of sync with the template that the stack is attempting to roll back to. To retry the rollback and resolve the error, you can use ContinueUpdateRollback.
Tip: To resolve the error, you might need to raise limits, change permissions, or modify other settings. For information on common errors that cause update rollback failures, see Update rollback failed.
In some cases, retrying the rollback doesn't resolve the error. In these cases, you must skip resources, and also acknowledge that these resources no longer reflect the desired state in the CloudFormation template. To skip the resources that caused the rollback failures, complete the following steps in the Resolution section.
至于错误的原因-您可以从CloudFormation消息中看到UserPoolClient的readAttributes和writeAttributes不能为空，就像您的情况一样.
我已将 google 登录添加到我的应用程序并尝试推送修改，但我没有这样做的权限。获得权限后，我尝试放大推送但出现此错误：
Stack:arn:aws:cloudformation:us-east-1:432853258441:stack/amplify-huruproject-local-190356/117b7360-c94d-11eb-a4cc-0e8a861a6983 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
推送操作发生错误：Stack:arn:aws:cloudformation:us-east-1:432853258441:stack/amplify-huruproject-local-190356/117b7360-c94d-11eb-a4cc-0e8a861a6983处于UPDATE_ROLLBACK_FAILED状态，无法更新。
问题是我在我的堆栈控制台中找不到这个特定的堆栈。我怎样才能解决这个问题？
更新：
我找到了堆栈，它在一个自动生成的嵌套堆栈中。
这是我发现的：
我不知道如何从这里开始。我应该删除整个堆栈吗？我会丢失所有数据吗？
根据 documentation，您可以删除堆栈或尝试继续回滚。最简单的解决方案是删除堆栈并重试。
摘要如下：
If your stack is stuck in the UPDATE_ROLLBACK_FAILED state after a failed update, then the only actions that you can perform on the stack are the ContinueUpdateRollback or DeleteStack operations. This is because CloudFormation requires further input from you to acknowledge that the stack is out of sync with the template that the stack is attempting to roll back to. To retry the rollback and resolve the error, you can use ContinueUpdateRollback.
Tip: To resolve the error, you might need to raise limits, change permissions, or modify other settings. For information on common errors that cause update rollback failures, see Update rollback failed.
In some cases, retrying the rollback doesn't resolve the error. In these cases, you must skip resources, and also acknowledge that these resources no longer reflect the desired state in the CloudFormation template. To skip the resources that caused the rollback failures, complete the following steps in the Resolution section.
至于错误的原因-您可以从CloudFormation消息中看到UserPoolClient的readAttributes和writeAttributes不能为空，就像您的情况一样.