Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda sedang melihat dokumentasi Apigee dan Apigee hybrid.
Tidak ada dokumentasi
Apigee Edge yang setara untuk topik ini.
Gejala
ApigeeIssue dengan ReasonAIS_VIRTUALHOST_MISSING_ENVGROUP ditampilkan saat melihat resource
di namespace apigee.
Pesan error
Setelah menjalankan kubectl -n apigee get apigeeissues, error
berikut akan ditampilkan:
NAME SEVERITY REASON DOCUMENTATION AGE
vhost-missing-eg-my-eg ERROR AIS_VIRTUALHOST_MISSING_ENVGROUP https://cloud.google.com/apigee/docs/api-platform/troubleshoot/playbooks/vh-missing-env-group 5h18m
Penyebab: Virtualhost tidak memiliki grup lingkungan
Salah satu virtualhosts yang ditentukan dalam overrides.yaml
tidak memiliki EnvironmentGroup yang sesuai.
Diagnosis
Jalankan perintah berikut:
kubectl -n apigee describe apigeeissue ISSUE_NAME
Dengan ISSUE_NAME adalah nama masalah. Misalnya,
vhost-missing-eg-my-eg.
Sesuatu yang mirip dengan berikut ini akan ditampilkan:
Pastikan untuk menyertakan semua setelan yang ditampilkan, termasuk --atomic
sehingga tindakan akan di-roll back jika gagal.
Penginstalan Anda mungkin telah atau belum disiapkan menggunakan
ENV_GROUP_RELEASE_NAME yang berbeda dari ENV_GROUP.
Untuk informasi tentang setelan, lihat
Menginstal Apigee hybrid menggunakan Helm.
Coba lagi dan pastikan pesan error tidak lagi
ditampilkan.
Harus mengumpulkan informasi diagnostik
Jika masalah berlanjut meskipun setelah mengikuti petunjuk di atas, kumpulkan informasi diagnostik berikut, lalu hubungi Layanan Pelanggan Google Cloud:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis documentation specifically addresses \u003ccode\u003eApigee hybrid\u003c/code\u003e and does not have an equivalent for \u003ccode\u003eApigee Edge\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe error \u003ccode\u003eAIS_VIRTUALHOST_MISSING_ENVGROUP\u003c/code\u003e indicates that a defined \u003ccode\u003evirtualhost\u003c/code\u003e in \u003ccode\u003eoverrides.yaml\u003c/code\u003e lacks a corresponding \u003ccode\u003eEnvironmentGroup\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve this issue, use the \u003ccode\u003ekubectl -n apigee describe apigeeissues ISSUE_NAME\u003c/code\u003e command to identify the missing \u003ccode\u003eEnvironmentGroup\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe problem can be corrected by either creating the missing \u003ccode\u003eEnvironmentGroup\u003c/code\u003e, or deleting the reference to the missing \u003ccode\u003eEnvironmentGroup\u003c/code\u003e from \u003ccode\u003eoverrides.yaml\u003c/code\u003e and reapplying the file via Helm.\u003c/p\u003e\n"],["\u003cp\u003eIf the problem continues after implementing the provided resolutions, you must gather specific diagnostic information, like the \u003ccode\u003eSpec.Details\u003c/code\u003e field of the \u003ccode\u003eApigeeIssue\u003c/code\u003e along with the Google Cloud project ID and the name of the Apigee hybrid organization, and contact Google Cloud Customer Care for further support.\u003c/p\u003e\n"]]],[],null,["# Virtual host missing environment group\n\n*You're viewing **Apigee** and **Apigee hybrid** documentation.\nThere is no equivalent\n[Apigee Edge](https://docs.apigee.com/api-platform/get-started/get-started) documentation for this topic.*\n| **Note:** This document is applicable for Apigee hybrid users only.\n\nSymptom\n-------\n\n\nAn `ApigeeIssue` with `Reason`\n`AIS_VIRTUALHOST_MISSING_ENVGROUP` is shown when viewing resources\nin the `apigee` namespace.\n\nError messages\n--------------\n\n\nAfter running `kubectl -n apigee get apigeeissues`, the following\nerror is displayed: \n\n```scdoc\nNAME SEVERITY REASON DOCUMENTATION AGE\nvhost-missing-eg-my-eg ERROR AIS_VIRTUALHOST_MISSING_ENVGROUP https://cloud.google.com/apigee/docs/api-platform/troubleshoot/playbooks/vh-missing-env-group 5h18m\n```\n\nCause: Virtualhost missing environment group\n--------------------------------------------\n\n\nOne of the `virtualhosts` defined in `overrides.yaml`\nis missing its corresponding `EnvironmentGroup`.\n\n### Diagnosis\n\n\nRun the following command: \n\n```\nkubectl -n apigee describe apigeeissue ISSUE_NAME\n```\n\n\nWhere \u003cvar translate=\"no\"\u003eISSUE_NAME\u003c/var\u003e is the name of the issue. For example,\n`vhost-missing-eg-my-eg`.\n\n\nSomething similar to the following is returned: \n\n```vb.net\nName: vhost-missing-eg-my-eg\nNamespace: apigee\nLabels: ais-reason=AIS_VIRTUALHOST_MISSING_ENVGROUP\nAnnotations: \u003cnone\u003e\nAPI Version: apigee.cloud.google.com/v1alpha1\nKind: ApigeeIssue\nMetadata:\n Creation Timestamp: 2023-04-05T14:29:38Z\n Generation: 1\n Managed Fields:\n API Version: apigee.cloud.google.com/v1alpha1\n Fields Type: FieldsV1\n fieldsV1:\n f:spec:\n .:\n f:details:\n f:documentation:\n f:reason:\n f:severity:\n Manager: apigeewatcher\n Operation: Update\n Time: 2023-04-05T14:29:38Z\n Resource Version: 28195\n UID: f7b62eb3-3f84-4a37-9ba8-9a0e1e9c3454\nSpec:\n Details: Expected EnvironmentGroup \"my-eg\" in ApigeeOrganization \"my-org\" for ApigeeRouteConfig \"my-org-my-eg\"\n Documentation: https://cloud.google.com/apigee/docs/api-platform/troubleshoot/playbooks/vh-missing-env-group\n Reason: AIS_VIRTUALHOST_MISSING_ENVGROUP\n Severity: ERROR\nEvents: \u003cnone\u003e\n``` \n\n```actionscript-3\nSpec:\n Details: Expected EnvironmentGroup \"my-eg\" in ApigeeOrganization \"my-org\" for ApigeeRouteConfig \"my-org-my-eg\"\n```\n\n\nThe contents of `Spec.Details` explains the name of the\n`EnvironmentGroup` that is expected to exist.\n\n### Resolution\n\n1. Use the `describe ApigeeIssue` command to display the name of the `EnvironmentGroup` which is expected to exist: \n\n ```\n kubectl -n apigee describe apigeeissues ISSUE_NAME\n ```\n\n\n Where \u003cvar translate=\"no\"\u003eISSUE_NAME\u003c/var\u003e is the name of the issue. For example,\n `vhost-missing-eg-my-eg`.\n\n\n In this example, the environment group `my-eg` is expected in\n the `my-org` Apigee organization.\n2. Use one of the following methods to correct the problem:\n 1. Create the environment group:\n 1. [Create an environment group](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#groups).\n 2. [Add an environment](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#adding).\n 3. [Create a proxy](/apigee/docs/api-platform/get-started/create-proxy).\n 4. [Deploy a proxy](/apigee/docs/api-platform/get-started/deploy-proxy) to that environment.\n 2. Delete the environment group:\n 1. Open `overrides.yaml` in a text editor.\n 2. Delete the removed environment group from the `virtualhosts`.\n 3. Save the `overrides.yaml` file.\n 4. Reapply the `overrides.yaml` file using the [Helm command](/apigee/docs/hybrid/latest/helm-reference):\n\n Dry run: \n\n ```\n helm upgrade ENV_GROUP_RELEASE_NAME apigee-virtualhost/ \\\n --namespace APIGEE_NAMESPACE \\\n --atomic \\\n --set envgroup=ENV_GROUP \\\n -f overrides.yaml \\\n --dry-run=server\n ```\n\n Make sure to include all of the settings shown, including `--atomic`\n so that the action rolls back on failure.\n\n Your installation may or may not have been set up using an\n \u003cvar translate=\"no\"\u003eENV_GROUP_RELEASE_NAME\u003c/var\u003e that differs from \u003cvar translate=\"no\"\u003eENV_GROUP\u003c/var\u003e.\n For information on the settings, see\n [Install Apigee hybrid using Helm](/apigee/docs/hybrid/latest/install-helm-charts).\n\n Install the chart: \n\n ```\n helm upgrade ENV_GROUP_RELEASE_NAME apigee-virtualhost/ \\\n --namespace APIGEE_NAMESPACE \\\n --atomic \\\n --set envgroup=ENV_GROUP \\\n -f overrides.yaml\n ```\n\n Retry and verify that the [error message](#error-messages) is no longer\n returned.\n\nMust gather diagnostic information\n----------------------------------\n\n\nIf the problem persists even after following the above instructions, gather\nthe following diagnostic information and then contact [Google Cloud Customer Care](https://cloud.google.com/support-hub/):\n\n1. The Google Cloud Project ID.\n2. The name of the Apigee hybrid organization.\n3. The `Spec.Details` field of the `ApigeeIssue`."]]
