我们已经设置了用于Google App部署的配置项,并且一直运行良好,直到昨天,我们在部署到Google App Engine时遇到了问题,错误如下所示:
ERROR: (gcloud.app.deploy) Error Response: [13] Flex operation projects/projectname/regions/asia-northeast1/operations/f26017a5-ade6-42a6-bd49-1ea287e086 error [INTERNAL]: An internal error occurred while processing task /appengine-flex-v1/update_flex_deployment/flex_update_resources>2018-10-02T01:19:39.513Z362: app_bucket_name is required.
Details: [
[
{
"@type": "type.googleapis.com/google.protobuf.Any",
"value": {
"@type": "type.googleapis.com/google.appengine.errors.AggregateDebugInfo",
"debugInfo": {
"stackEntries": [
"java.lang.IllegalStateException: app_bucket_name is required.",
"\tat com.google.common.base.Preconditions.checkState(Preconditions.java:507)",
"\tat com.google.apphosting.admin.flex.resources.deployment.UpdateResourcesProducerModule.produceWriteGcsMetadata(UpdateResourcesProducerModule.java:323)",
"\tSuppressed: com.google.common.util.concurrent.UncheckedExecutionException: ",
"\t\tat com.google.apps.framework.producers.Present.checkSucceeded(Present.java:54)",
"\t\tat com.google.apphosting.admin.flex.resources.deployment.UpdateResourcesProducerModule.patchDmDeployment(UpdateResourcesProducerModule.java:347)",
"\tSuppressed: com.google.common.labs.concurrent.LabsFutures$10: GraphFuture{key=@com.google.apps.framework.producers.PrivateVisibility(annotation=\"@com.google.apphosting.admin.flex.resources.deployment.UpdateResourcesProducerModule$NarrowUpdateTargetDm\", module=com.google.apphosting.admin.flex.resources.deployment.UpdateResourcesProducerModule.class) com.google.apphosting.admin.flex.lib.dm.internal.proto.Deployment} failed: java.lang.IllegalStateException: app_bucket_name is required.",
"\t\tat com.google.apps.framework.producers.PresentImpl.get(PresentImpl.java:29)",
"\t\tat com.google.apphosting.admin.flex.resources.deployment.UpdateResourcesProducerModule.narrowDmUpdated(UpdateResourcesProducerModule.java:444)"
]
}
}
}
]
]
Exited with code 1
有人知道我们可以解决这个问题吗?
P / S:这与Google最近推出的cloud-tasks有关吗?
答案 0 :(得分:2)
根据Google Issue Tracker中的建议:
嗨,当您尝试部署时,您是否覆盖了现有版本?如果是,您可以尝试使用新名称而不是覆盖它来部署一个版本吗?您观察到的错误似乎是一个已知问题,因此当App Engine工程团队着手解决此问题时,这将是暂时的解决方法。
我尝试部署到新版本,并且可以使用,然后将其切换回覆盖现有版本,然后又可以使用。 (*也适用于其他应用程序。)
尽管如此,我们仍然不确定造成此突然问题的原因是什么。
P / S:我还通过“ Storage Legacy Bucket Owner”向存储桶中的CI服务添加了权限