Unable to resolve project from metadata server for GCE discovery service – How to solve related issues

Unable to resolve project from metadata server for GCE discovery service – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Unable to resolve project from metadata server for GCE discovery service ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cloud-aws, discovery, discovery-gce, instances and metadata.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Unable to resolve project from metadata server for GCE discovery service” classname is GceInstancesServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        try {
            // this code is based on a private GCE method: {
link com.google.cloud.ServiceOptions#getAppEngineProjectIdFromMetadataServer()}
            return getAppEngineValueFromMetadataServer("/computeMetadata/v1/project/project-id");
        } catch (Exception e) {
            logger.warn("unable to resolve project from metadata server for GCE discovery service"; e);
        }
        return null;
    }

    private List resolveZones() {



 

Run the Check-Up to get a customized report like this:

Analyze your cluster