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

Failing test(s): TestAccDataLossPreventionDiscoveryConfig_Update #18004

Open
SarahFrench opened this issue May 2, 2024 · 6 comments
Open

Failing test(s): TestAccDataLossPreventionDiscoveryConfig_Update #18004

SarahFrench opened this issue May 2, 2024 · 6 comments
Labels
forward/review In review; remove label to forward service/dlp size/s test-failure test-failure-50 50%+ fail rate
Milestone

Comments

@SarahFrench
Copy link
Member

Impacted tests

  • TestAccDataLossPreventionDiscoveryConfig_Update

Affected Resource(s)

  • google_data_loss_prevention_discovery_config

Failure rates

  • 80% since 2024-04-18

Message(s)

    vcr_utils.go:152: Step 1/4 error: Error running apply: exit status 1
        Error: Error creating DiscoveryConfig: googleapi: Error 400: All discovery configs must be in the same location, but one already exists in [us]
          with google_data_loss_prevention_discovery_config.basic,
          on terraform_plugin_test.tf line 14, in resource "google_data_loss_prevention_discovery_config" "basic":
          14: resource "google_data_loss_prevention_discovery_config" "basic" {

Nightly build test history

@github-actions github-actions bot added forward/review In review; remove label to forward service/dlp labels May 2, 2024
@SarahFrench
Copy link
Member Author

Looks like it could be an issue with sweeping up dangling resources, but would need to double-check the test's config and debug logs from the test

@SarahFrench SarahFrench added the test-failure-50 50%+ fail rate label May 2, 2024
@BBBmau BBBmau added this to the Goals milestone May 6, 2024
@BBBmau BBBmau added the size/s label May 6, 2024
@patrickmoy
Copy link

This could also possibly be due to tests running in parallel, though the update tests in resource_data_loss_prevention_discovery_config_test.go are set to run serially to prevent this from happening...

@melinath
Copy link
Collaborator

There are a number of other DLP tests - do they also need to be forced to run in serial maybe?

@patrickmoy
Copy link

No, our service restriction of one config per region per storage type only applies to DiscoveryConfig resources, so this is new.

I believe it's the example tests running simultaneously with the update tests, I found some similar merged PRs that required serial tests, but some opt to use "skip_test" on their examples. I could take a stab at that and see if it resolves.

@patrickmoy
Copy link

Can we confirm that there is still flakiness? GoogleCloudPlatform/magic-modules#10798 should have addressed this to some degree

@melinath
Copy link
Collaborator

It's still definitely flakey - hard to say yet if it's better than it was previously or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
forward/review In review; remove label to forward service/dlp size/s test-failure test-failure-50 50%+ fail rate
Projects
None yet
Development

No branches or pull requests

4 participants