Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeout and waring about using actions #26

Open
darkn3rd opened this issue Jul 23, 2022 · 0 comments
Open

Timeout and waring about using actions #26

darkn3rd opened this issue Jul 23, 2022 · 0 comments

Comments

@darkn3rd
Copy link

darkn3rd commented Jul 23, 2022

Steps to Reproduce

PROJECT_ID="my-cicd-project" # change this to desired project name
gcloud config set project $PROJECT_ID
PROJECT_NUM=$gcloud projects describe $PROJECT_ID --format="value(projectNumber)"
gcloud projects add-iam-policy-binding $PROJECT_ID \
  --member serviceAccount:$PROJECT_NUM@cloudservices.gserviceaccount.com --role roles/owner
gcloud services enable \
  deploymentmanager.googleapis.com \
  sqladmin.googleapis.com \
  iam.googleapis.com \
  cloudresourcemanager.googleapis.com \
  runtimeconfig.googleapis.com \
  compute.googleapis.com

gcloud compute images create "flatcar-stable" \
  --source-image-family "flatcar-stable" \
  --source-image-project "kinvolk-public"

git clone git@github.com:JetBrains/teamcity-google-template.git
sed -i 's/IPv4Range.*/autoCreateSubnetworks: true/' teamcity-google-template/network.jinja

DEPLOYMENT_NAME="tc-server"
ZONE="us-central1-a"
gcloud deployment-manager deployments create $DEPLOYMENT_NAME \
  --template ./teamcity-google-template/teamcity.jinja \
  --properties zone:$ZONE

Expected Results

These scripts would work.

Actual Results

When running these scripts, it seemed to get stuck on creating a network, which I am not sure why this is actually needed. I found out later that this ran up against a quote. Creating a new network creates a VPC, which then creates subnets across all regions.

ERROR: (gcloud.deployment-manager.deployments.create) Wait for Operation [operation-1658558492916-5e4733dcf3987-eed04cd5-674edd2d] exceeded timeout [1200].

When I looked at the deployment in the web console, I saw this:

The deployment uses actions, which are an unsupported feature. We recommend that you avoid using actions. For more information visit: https://cloud.google.com/deployment-manager/docs/migrations/actions Examples of actions used (some actions may not be in this list): gcp-types/sqladmin-v1beta4:sql.users.delete, gcp-types/cloudresourcemanager-v1:cloudresourcemanager.projects.getIamPolicy, gcp-types/cloudresourcemanager-v1:cloudresourcemanager.projects.setIamPolicy
This deployment has resources from the Runtime Configurator service, which is in Beta. There is no planned date for moving this feature into General Availability (GA). Examples of runtimeconfig types used: runtimeconfig.v1beta1.config, runtimeconfig.v1beta1.waiter 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant