Create VM instance "[some name]" and its boot disk "[some disk name]" fails

Google Cloud Cloud Foundations & Onboarding
1

One or more of the service account scopes are invalid: 'https://www.googleapis.com/auth/devstorage.read_only
https://www.googleapis.com/auth/logging.write
https://www.googleapis.com/auth/monitoring.write
https://www.googleapis.com/auth/servicecontrol
https://www.googleapis.com/auth/service.management.readonly
https://www.googleapis.com/auth/trace.append’

The VM Instance is created based on a Instance template created recently - IF I use my old instance template it works fine.

What update or change has I missed to read to not being able to solve this?

2

Could you specify exactly what commands/recipes you are executing? I’m not quite following the nature of the puzzle. If you could capture exactly what steps you performed and what you are finding then that may help us to interpret the puzzle or provide a framework for us to attempt to test it in our environment to achieve a recreate.

3

I create a container locally on my Windows PC - pushing the container to GCP with:

docker tag [image] eu.gcr.io/[project]/[name]:v1
docker push eu.gcr.io/[project]/[name]:v1

After pusing: Through the GCP WebSite I create an new Instance template with the newly pushed image. (With my Google user account, who is “Owner” on the project)

Finding my instance group, and using: https://console.cloud.google.com/compute/instanceGroups/edit/[…]

to edit the instance group.

In Edit i select the newly create “instance template”.

And press “Save”.

The error above occurs.

4

What I i’m think I am hearing is that we have two instance templates … one where you create a Compute Engine it works and the other it doesn’t. Maybe we could use the command line in a Cloud Shell instance and get a detailed description of the two instance templates and examine them in detail. The following is a link to the gcloud documentation for a CLI program that can be used to obtain the details of instance templates. Maybe if we run this command against each template and compare the two we can get an “aha” moment:

https://cloud.google.com/sdk/gcloud/reference/compute/instance-templates/describe

5

Yes two instance template (“old” and “new”)

“old” is being used by the instance group.

I try to replace “old” with “new” in the Instance Group - and recycle the Compute engines in the process.

I try to do the replace via GCP Console or CLI (Same error).

This methods worked in August 2021

6

The issue was my “Upload script” gotten from Google Cloud console was stating “Scopes” - the scopes was removed and the rights was set to default.