Invalid value for field 'region': 'asia-northeast3'. Unknown region."

[lukasschwab]

Environment details

• OS: Mac OS 10.14
• Node.js version: v13.3.0
• npm version: 6.13.2
• @google-cloud/compute version: 1.1.8

Steps to reproduce

const compute = new Compute({
  credentials,
  projectId
});
const [networks] = await compute.getNetworks();
const network = networks[0];
const [subnets] = await network.getSubnetworks();

await Promise.all(subnets.map(subnet => subnet.getMetadata()))

This yields a 400 error with the message Invalid value for field 'region': 'asia-northeast3'. Unknown region..

Indeed, gcloud compute regions list does not list asia-northeast3, and it is not listed in the regions documentation.

asia-northeast3 is listed in the Console:

[lukasschwab]

Perhaps this should be filed with the Compute team rather than with the client library; happy to re-file/redundantly file it.

[JustinBeckwith]

Greetings! I would be surprised if this was specific to the library, as you mentioned. One thing that makes it easier to pin down - can you reproduce the issue using the API explorer?
https://cloud.google.com/compute/docs/reference/rest/v1/

If you can reproduce the problem there, it makes things clear the underlying API is the culprit. With a basic test, I was unable to reproduce this sadly.

If it does turn out to be a Compute Engine problem - you want to start with support if you have a support contract, or otherwise file an issue here:
https://issuetracker.google.com/savedsearches/559755

Hope this helps! Let us know how things go :)

[lukasschwab]

I was unable to reproduce the error in the API explorer this morning; I reverted my work-around, and the error is no longer occurring in my project either.

Seems that this was a blip in the underlying API:

• Boskos seems to be wedged tektoncd/plumbing#186
  • Mentions: "It looks like the consensus is that gcloud itself had an outage (i.e. the API it communicates with)."
• Temporary janitor zone hack. kubernetes/test-infra#15951

Using the API explorer to distinguish between client and API errors is clever––I'll use it in the future.

Thanks for the reply!

[hermes2014]

This issue doesn't seem to be the problem with the Node.js API. The same error occurs when trying to create an instance in the Seoul region in the GCP web interface.

요청에 잘못된 인수가 포함됨: 'Invalid value for field 'zone': 'asia-northeast3-a'. Unknown zone..' 오류 코드: 'invalid'

It seems that the GCP Seoul Region is not fully ready yet. I have to wait a little longer.

[rudebono]

me too,
still error occur

[yhware]

@lukasschwab Hey do you mind opening the issue up again? I'm facing the same issue even with the latest sdk with the following error.

ERROR: (gcloud.compute.networks.subnets.create) Could not fetch resource:

• Invalid value for field 'region': 'asia-northeast3'. Unknown region.

[JustinBeckwith]

Greetings! This is mostly not an issue with the npm module, and rather a problem with the API. Please see #390 (comment)

[gneyal]

I'm also getting Invalid value for region: us-east1-c