Failing test(s): TestAccBigqueryDataTransferConfig

[SarahFrench]

Failure rates

• 100% since 2023-09-27 - new type of failure

Impacted tests

• TestAccBigqueryDataTransferConfig

Affected Resource(s)

• google_bigquery_data_transfer_config

Nightly build test history

• Link

Message(s)

------- Stdout: -------
=== RUN   TestAccBigqueryDataTransferConfig
=== RUN   TestAccBigqueryDataTransferConfig/booleanParam
=== RUN   TestAccBigqueryDataTransferConfig/update_params
=== RUN   TestAccBigqueryDataTransferConfig/update_service_account
=== RUN   TestAccBigqueryDataTransferConfig/basic
=== RUN   TestAccBigqueryDataTransferConfig/update
    vcr_utils.go:152: Step 2/5 error: Error running apply: exit status 1
        Error: Error updating Config "projects/594424405950/locations/asia-northeast1/transferConfigs/6514c398-0000-2c7f-9fe7-883d24fe0948": googleapi: Error 400: The requested service account name () doesn't exist.
          with google_bigquery_data_transfer_config.query_config,
          on terraform_plugin_test.tf line 25, in resource "google_bigquery_data_transfer_config" "query_config":
          25: resource "google_bigquery_data_transfer_config" "query_config" {
=== RUN   TestAccBigqueryDataTransferConfig/service_account
=== RUN   TestAccBigqueryDataTransferConfig/no_destintation
--- FAIL: TestAccBigqueryDataTransferConfig (257.90s)
    --- PASS: TestAccBigqueryDataTransferConfig/booleanParam (34.18s)
    --- PASS: TestAccBigqueryDataTransferConfig/update_params (31.37s)
    --- PASS: TestAccBigqueryDataTransferConfig/update_service_account (60.29s)
    --- PASS: TestAccBigqueryDataTransferConfig/basic (33.11s)
    --- FAIL: TestAccBigqueryDataTransferConfig/update (39.01s)
    --- PASS: TestAccBigqueryDataTransferConfig/service_account (30.49s)
    --- PASS: TestAccBigqueryDataTransferConfig/no_destintation (29.45s)
FAIL

b/303808513

[SarahFrench]

Previously these tests failed due to a missing permission, which appears to be related to how the GA nightly tests were configured with Beta credentials for a period. Now the credentials are fixed the error shown above has occurred

[cleentfaar]

@SarahFrench we are running into the same error when running terraform apply on google_bigquery_data_transfer_config resources, in particular when we do it a second time (updates):

Error updating Config "...": googleapi: Error 400: The requested service account name () doesn't exist.

I noticed that if we specify a value for the service_account_name argument, it works again. It seems google no longer falls back to the SA that is running the terraform apply, and needs it to be specified explicitly? But only for updates, so sounds more like a bug?

[kickingfish]

We are getting the same error message. This is happening when the provider is upgraded to 4.84.0. If the 4.84.0 is used initially (not from upgrade), there is no issue.

The error happened with or without explicitly setting value for the service_account_name .

[kickingfish]

I just tested the 5.0.0, it is still giving me the error -- Error: Error updating Config "projects/304937331054/locations/us/transferConfigs/653202dd-0000-236e-8fc1-94eb2c1bd542": googleapi: Error 400: The requested service account name () doesn't exist.

[kitagry]

I think this error occurs from #15359.

I tried the following step

1. create google_bigquery_data_transfer_config : ok
2. change google_bigquery_data_transfer_config and update this: NG
   • error message is Error 400: The requested service account name () doesn't exist.

I think it is because updateMasks includes service_account_name whether service_account_name is empty or not. And if we don't set service_account_name explicitly, it try to update service_account_name to "".

[kickingfish]

Do we have an ETA for the fix? @SarahFrench

[SarahFrench]

I'll add a bug report separate to this issue

[SarahFrench]

Please follow #16126 for updates on this bug as it goes through our triage process

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.