{
  "id": "cloud/gcp-cloud-run-efs-mount-missing",
  "signature": "Failed to mount EFS filesystem: resource temporarily unavailable",
  "signature_zh": "无法挂载EFS文件系统：资源暂时不可用",
  "regex": "Failed to mount EFS filesystem: resource temporarily unavailable",
  "domain": "cloud",
  "category": "runtime_error",
  "subcategory": null,
  "root_cause": "Cloud Run service cannot mount an EFS file system because the VPC connector is misconfigured or the EFS mount target is in a different subnet without proper routing.",
  "root_cause_type": "generic",
  "root_cause_zh": "Cloud Run服务无法挂载EFS文件系统，因为VPC连接器配置错误或EFS挂载目标位于不同子网且缺少正确路由。",
  "versions": [
    {
      "version": "Cloud Run (managed) gcloud 450.0.0",
      "introduced": null,
      "deprecated": null,
      "removed": null,
      "behavior_change": null,
      "status": "active"
    },
    {
      "version": "AWS EFS (via VPC connector)",
      "introduced": null,
      "deprecated": null,
      "removed": null,
      "behavior_change": null,
      "status": "active"
    }
  ],
  "os_specific": {},
  "dead_ends": [
    {
      "action": "Increase Cloud Run memory limit",
      "why_fails": "Memory limit does not affect NFS mount availability; the error is network-related.",
      "fail_rate": 0.6,
      "condition": "",
      "sources": []
    },
    {
      "action": "Recreate the EFS file system",
      "why_fails": "The file system itself is healthy; the issue is in the network path between Cloud Run and EFS.",
      "fail_rate": 0.8,
      "condition": "",
      "sources": []
    }
  ],
  "workarounds": [
    {
      "action": "Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR.",
      "success_rate": 0.75,
      "how": "Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR.",
      "condition": "",
      "sources": []
    },
    {
      "action": "Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28`",
      "success_rate": 0.85,
      "how": "Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28`",
      "condition": "",
      "sources": []
    }
  ],
  "workarounds_zh": [
    "Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR.",
    "Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28`"
  ],
  "transition_graph": {
    "leads_to": [],
    "preceded_by": [],
    "frequently_confused_with": []
  },
  "official_doc_url": "https://cloud.google.com/run/docs/configuring/vpc-connectors",
  "official_doc_section": null,
  "error_code": "EFSMountError",
  "verification_tier": "ai_generated",
  "confidence": 0.85,
  "fix_success_rate": 0.78,
  "resolvable": "true",
  "first_seen": "2024-03-15",
  "last_confirmed": "2024-06-01",
  "last_updated": "2024-06-01",
  "evidence_count": 1,
  "tags": [],
  "locale": "en",
  "aliases": []
}