Ádám Szita created HIVE-22659:
---------------------------------
Summary: JCoud needs to be updated to 2.1.3 in ptest
Key: HIVE-22659
URL: https://issues.apache.org/jira/browse/HIVE-22659
Project: Hive
Issue Type: Bug
Reporter: Ádám Szita
Assignee: Ádám Szita
Since a couple of days ptest responded 404 to test queries coming in from
jenkins side.
I took a look into the issue and saw this exception on
hiveptest-server-upstream side:
{code:java}
Caused by: java.lang.IllegalStateException: zone
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-central1-d
not present in
[https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-east1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-east1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-east1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-east2-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-east2-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-east2-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-northeast1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-northeast1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-northeast1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-northeast2-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-northeast2-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-northeast2-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-south1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-south1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-south1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-southeast1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-southeast1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/asia-southeast1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/australia-southeast1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/australia-southeast1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/australia-southeast1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-north1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-north1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-north1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west1-d
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west2-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west2-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west2-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west3-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west3-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west3-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west4-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west4-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west4-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west6-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west6-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/europe-west6-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/northamerica-northeast1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/northamerica-northeast1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/northamerica-northeast1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/southamerica-east1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/southamerica-east1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/southamerica-east1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-central1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-central1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-central1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-central1-f
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-east1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-east1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-east1-d
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-east4-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-east4-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-east4-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-west1-a
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-west1-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-west1-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-west2-c
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-west2-b
https://www.googleapis.com/compute/v1/projects/gcp-hive-upstream/zones/us-west2-a]
{code}
Debugging into the issue, it seems like that when we we put our cloud context
in place for test execution, some default values originating from default
templates are matched with actual GCP capabilities - and I guess zone
us-central-1d was decommissioned in real-life, hence the exception.
I upgraded jclouds version from 2.1.0 to 2.1.3 on server side and retried
running Tomcat with this new installation. It seems to have fixed the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
