Cloud Volumes ONTAP

TF provider NetApp/netapp-cloudmanager/21.3.0 fails to build a connector

pzi123321
1,322 Views

Simple try to build a Cloud Manager connector in GCP fails half way after creating a deployment in GCP, boot disk and then when trying to label the disk it fails leaving open deployment and disk behind.  The error message in GCP activity after successful creation of boot disk is:

Failed: Set labels of disk

Failed: Set labels of disk
xxxxxx@cloudservices.gserviceaccount.com failed to set labels of disk clgx-netapplab-dev-vm-disk-boot
April 2, 2021 at 9:39:32 PM GMT-6

User
    xxxxxxx@cloudservices.gserviceaccount.com


Resource name
    projects/netapplab-app-dev-49c4/zones/us-west1-a/disks/netapplab-dev-vm-disk-boot

Error message
    Invalid argument (HTTP 400): Labels fingerprint either invalid or resource labels have changed

Response > error
Code
    412
Errors
Errors 1
Domain
    global
Location
    If-Match
Location type
    header
Message
    Labels fingerprint either invalid or resource labels have changed
Reason
    conditionNotMet
Message
    Labels fingerprint either invalid or resource labels have changed

 

The TF code is here:

terraform {
  required_providers {
    netapp-cloudmanager = {
      source = "NetApp/netapp-cloudmanager"
      version = "21.3.0"
    }
  }
}


provider "netapp-cloudmanager" {
  refresh_token = var.cloudmanager_refresh_token
}


resource "netapp-cloudmanager_connector_gcp" "this" {
  provider              = netapp-cloudmanager
  name                  = var.project_name
  project_id            = var.project_id
  zone                  = var.zone
  company               = "x"
  service_account_email = var.service_account_email
  service_account_path  = var.service_account_path
  account_id            = var.account_id
}

 

1 ACCEPTED SOLUTION

pzi123321
1,235 Views

It turned out that this disk label error was non fatal and the connector build was failing after that on wrong subnet_id provided.

My successful builds still show this error in activity reports but work fine. It can be ignored - I think.

View solution in original post

1 REPLY 1

pzi123321
1,236 Views

It turned out that this disk label error was non fatal and the connector build was failing after that on wrong subnet_id provided.

My successful builds still show this error in activity reports but work fine. It can be ignored - I think.

Public