本文介绍了GCP作曲者创建失败，请求失败的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
尝试使用gcloud CLI创建GCP composer环境实例
Trying to create GCP composer environment instance with gcloud CLI
gcloud composer environments create "jakub" \
> --project "projectX" \
> --location "us-central1" \
> --zone "us-central1-a" \
> --disk-size 50GB \
> --node-count 3 \
> --image-version composer-1.7.1-airflow-1.10.2 \
> --machine-type n1-standard-2 \
> --python-version 3 \
> --labels env="test"
一个小时后出现错误:
f7b3f4-6b95-4fb0-85e3-f39a2b11cec9] failed: Http error status code: 400
Http error message: BAD REQUEST
Additional errors:
{"ResourceType":"appengine.v1.version","ResourceErrorCode":"400","ResourceErrorMessage":{"code":400,"message":"Legacy health checks are no longer supported for the App Engine Flexible environment. Please remove the 'health_check' section from your app.yaml and configure updated health checks. For instructions on migrating to split health checks see https://cloud.google.com/appengine/docs/flexible/java/migrating-to-split-health-checks","status":"INVALID_ARGUMENT","details":[],"statusMessage":"Bad Request","requestPath":"https://appengine.googleapis.com/v1/apps/vd41e6cad4ccb2a7b-tp/services/default/versions","httpMethod":"POST"}}
基于 https://cloud.google.com/sdk /gcloud/reference/composer/environments/create
推荐答案
这是由于尝试使用旧的图像版本而引起的.根据受支持的Cloud Composer，使用新的受支持版本重试Composer Environment创建版本.
This is caused because you are trying to use an old image version. Retry Composer Environment creation with a newer supported version as per Supported Cloud Composer versions.
这篇关于GCP作曲者创建失败，请求失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！