L'istanza non segnala lo stato del gruppo di ambienti
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Stai visualizzando la documentazione di Apigee e Apigee hybrid.
Visualizza la documentazione di
Apigee Edge.
Sintomi
I deployment dei proxy API non riescono con un errore Instance INSTANCE_NAME
is not reporting status for environment group ENV_GROUP_NAME
nell'interfaccia utente di Apigee hybrid.
Messaggi di errore
L'errore The Instance INSTANCE_NAME is not reporting status for environment group
ENV_GROUP_NAME viene visualizzato nel menu Proxy API nella scheda Panoramica quando passi il mouse sopra il punto esclamativo rosso visualizzato nella colonna Stato della sezione Deployment:
Quando utilizzi l'ingresso Apigee, il file overrides.yaml deve avere il selezionatore app: apigee-ingressgateway nella sezione virtualhosts
Causa: manca il selettore app: apigee-ingressgateway
Quando utilizzi il gateway di ingresso Apigee, il file overrides.yaml include una sezione per la configurazione di virtualhosts in cui è necessario configurare il selettore app: apigee-ingressgateway.
Diagnosi
Innanzitutto, verifica di utilizzare il gateway di ingresso Apigee disponibile con la versione Hybrid 1.8 e successive (la seguente configurazione non funziona per l'ASM Istio gestito dal cliente). Nel
overrides.yaml file che include il gruppo di ambienti menzionato nell'errore, individua la
virtualhosts sezione e controlla se mancano i seguenti selettori:
Assicurati di includere tutte le impostazioni mostrate, inclusa --atomic
in modo che l'azione venga ripristinata in caso di errore.
L'installazione potrebbe o meno essere stata configurata utilizzando un
ENV_GROUP_RELEASE_NAME diverso da ENV_GROUP.
Per informazioni sulle impostazioni, consulta
Installare Apigee Hybrid utilizzando Helm.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eThis document addresses an error specific to Apigee hybrid users where API proxy deployments fail, displaying an "Instance is not reporting status for environment group" error.\u003c/p\u003e\n"],["\u003cp\u003eThe root cause of this issue is identified as a missing \u003ccode\u003eapp: apigee-ingressgateway\u003c/code\u003e selector within the \u003ccode\u003evirtualhosts\u003c/code\u003e section of the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file when using the Apigee ingress gateway.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve the error, users must edit their \u003ccode\u003eoverrides.yaml\u003c/code\u003e file to include the \u003ccode\u003eapp: apigee-ingressgateway\u003c/code\u003e selector under the \u003ccode\u003evirtualhosts\u003c/code\u003e section, along with the \u003ccode\u003eingress_name\u003c/code\u003e selector.\u003c/p\u003e\n"],["\u003cp\u003eAfter updating the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file, the changes should be applied using Helm, following the provided commands for a dry run and then the final installation.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee hybrid ingress gateway version must be 1.8 or later, and the fix doesn't work for customer-managed Istio ASM, as confirmed before applying the fix.\u003c/p\u003e\n"]]],[],null,["# Instance is not reporting status for environment group\n\n*You're viewing **Apigee** and **Apigee hybrid** documentation.\nView [Apigee Edge](https://docs.apigee.com/api-platform/troubleshoot/support-d) documentation.*\n| **Note:** This document is applicable for Apigee hybrid users only.\n\nSymptoms\n--------\n\n\nDeployments of API proxies fail with `Instance `\u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e`\nis not reporting status for environment group `\u003cvar translate=\"no\"\u003eENV_GROUP_NAME\u003c/var\u003e error\nin the Apigee hybrid UI.\n\nError Messages\n--------------\n\n\n`The Instance `\u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e` is not reporting status for environment group\n`\u003cvar translate=\"no\"\u003eENV_GROUP_NAME\u003c/var\u003e error is displayed in the **API proxies** menu under the\n**Overview** tab when hovering over the red exclamation mark appearing in the **Status**\ncolumn of **Deployments** section:\n\nPossible Causes\n---------------\n\n### Cause: The selector `app: apigee-ingressgateway` is missing\n\n\nWhen using the Apigee ingress gateway, the `overrides.yaml` file includes a section for\n`virtualhosts` configuration in which the selector `app: apigee-ingressgateway` needs\nto be configured.\n\n#### Diagnosis\n\n\nFirst, confirm that you are using the Apigee ingress gateway which is available with Hybrid version\n1.8 and later (the following configuration does not work for customer-managed Istio ASM). In your\n`overrides.yaml` file which includes the environment group mentioned in the error, find the\n`virtualhosts` section and check if the following selectors are missing: \n\n```scdoc\n selector:\n app: apigee-ingressgateway\n ingress_name: INGRESS_NAME\n```\n\n#### Resolution\n\n\nEdit the `overrides.yaml` file so that the `virtualhosts[].selector` section\nlooks similar to the following example: \n\n```scdoc\n virtualhosts:\n - name: my-environment-group\n sslCertPath: my-cert.crt\n sslKeyPath: my-cert.key\n selector:\n app: apigee-ingressgateway\n ingress_name: \u003cvar translate=\"no\"\u003eINGRESS_NAME\u003c/var\u003e\n \n```\n\nAfter editing the `overrides.yaml` file apply the new configuration using\n[Helm](/apigee/docs/hybrid/latest/helm-reference):\n\nDry run: \n\n```\nhelm upgrade ENV_GROUP_RELEASE_NAME apigee-virtualhost/ \\\n--namespace APIGEE_NAMESPACE \\\n--atomic \\\n--set envgroup=ENV_GROUP \\\n-f OVERRIDES_FILE \\\n--dry-run=server\n```\n\nMake sure to include all of the settings shown, including `--atomic`\nso that the action rolls back on failure.\n\nYour 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.\nFor information on the settings, see\n[Install Apigee hybrid using Helm](/apigee/docs/hybrid/latest/install-helm-charts).\n\nInstall the chart: \n\n```\nhelm upgrade ENV_GROUP_RELEASE_NAME apigee-virtualhost/ \\\n--namespace APIGEE_NAMESPACE \\\n--atomic \\\n--set envgroup=ENV_GROUP \\\n-f OVERRIDES_FILE\n```\n\nReferences\n----------\n\n- [Mapping virtual hosts to Apigee ingress gateway deployments](/apigee/docs/hybrid/v1.10/managing-ingress#targetvh)"]]
