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): TestAccTPUNode_tpuNodeBUpdateTensorFlowVersion (cidr range conflict) #10223

Closed
melinath opened this issue Oct 1, 2021 · 3 comments · Fixed by GoogleCloudPlatform/magic-modules#5432

Comments

@melinath
Copy link
Collaborator

melinath commented Oct 1, 2021

Failure rate: 100% in Sept 2021

Impacted tests:

  • TestAccTPUNode_tpuNodeBUpdateTensorFlowVersion

Nightly builds:

Message:

=== RUN   TestAccTPUNode_tpuNodeBUpdateTensorFlowVersion
      === PAUSE TestAccTPUNode_tpuNodeBUpdateTensorFlowVersion
      === CONT  TestAccTPUNode_tpuNodeBUpdateTensorFlowVersion
          provider_test.go:278: Step 1/4 error: Error running apply: exit status 1
              
              Error: Error waiting to create Node: Error waiting for Creating Node: Error code 3, message: Cloud TPU received an invalid argument. The 'CIDR Range' value "10.1.0.0/29" on network "<network-id>" conflicts with another subnet or object in the (peered) customer network.
              
                on terraform_plugin_test.tf line 5, in resource "google_tpu_node" "tpu":
                 5: resource "google_tpu_node" "tpu" {
              
              
      --- FAIL: TestAccTPUNode_tpuNodeBUpdateTensorFlowVersion (27.00s)
      FAIL

Note: This is separate from issues with TPU Node capacity captured by #10222

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 11, 2021
@melinath melinath reopened this Sep 9, 2022
@melinath
Copy link
Collaborator Author

melinath commented Sep 9, 2022

@melinath
Copy link
Collaborator Author

melinath commented Sep 9, 2022

actually I'll open this as a separate issue.

@melinath melinath closed this as completed Sep 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants