问题描述
由于以下错误，无法正确删除Cloud Composer:
Cloud Composer is not getting deleted properly with this error:
由于所需的预操作尚未完成，RPC已跳过.
RPC Skipped due to required preoperation not finished yet.
这是错误屏幕截图:
here's the error screenshot:
推荐答案
请按照以下步骤手动删除环境资源:
Please, follow the below steps to delete environments resources manually:
- 删除与环境相对应的GKE集群
- 删除环境使用的Google存储桶
- 使用以下方法删除相关的部署:
gcloud deployment-manager deployments delete <DEPLOYMENT_NAME> --delete-policy=ABANDON
- 然后再次尝试通过以下方式删除Composer环境:
gcloud composer environments delete <ENVIRONMENT_NAME> --location <LOCATION>
您面临的问题还可能与项目中Cloud Composer服务帐户的配置错误有关.默认情况下，Cloud Composer环境以Compute Engine默认服务帐户运行，但是当您使用自定义服务帐户时，至少该服务帐户需要composer.worker 角色用于访问Cloud Composer环境中的资源.请参阅本文档以获取有关如何操作的更多详细信息授予服务帐户角色.
The problem you are facing could be also related with a misconfiguration with the Cloud Composer service account in your project. By default, Cloud Composer environments run as the Compute Engine default service account, but when you are using a custom service account, at a minimum, that service account requires the permissions that the composer.worker role provides to access resources in the Cloud Composer environment. Please refer to this documentation for further details about how to grant a role to a service account.
请尝试添加政策绑定，将Cloud Composer API服务代理角色分配给服务帐户，因此命令为:
Please, try to add the policy binding for Cloud Composer API Service Agent role to the service account, so the command would be:
gcloud projects add-iam-policy-binding <PROJECT_ID> --member=<MEMBER> --role=roles/composer.serviceAgent
member的格式应为user|group|serviceAccount:email或domain:domain(请参阅文档).
The member should be of the form user|group|serviceAccount:email or domain:domain (refer to documentation).
然后，请重试删除Composer环境的操作.希望以上信息对您有用.
Then, please retry the action of remove your Composer environments. I hope you find the above pieces of information useful.
这篇关于Cloud Composer没有被删除的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！