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

Delegated Resolver test destroy fails to destroy #776

Open
MatthewLemmond opened this issue May 3, 2024 · 2 comments
Open

Delegated Resolver test destroy fails to destroy #776

MatthewLemmond opened this issue May 3, 2024 · 2 comments
Labels
bug 🐞 Something isn't working internal-synced

Comments

@MatthewLemmond
Copy link
Member

Affected modules

  • terraform-ibm-landing-zone-vpc

Terraform CLI and Terraform provider versions

Terraform v1.5.7
on darwin_amd64

  • provider registry.terraform.io/hashicorp/time v0.11.1
  • provider registry.terraform.io/ibm-cloud/ibm v1.64.2

Terraform output

output.txt

Debug output

Expected behavior

test should destroy the spoke vpc and its DNS resolution bindings before attempting to delete the hub vpc or its custom resolver

Actual behavior

Error is encountered due to the destroy being apparently run out of order (see attached output.txt)

Steps to reproduce (including links and screen captures)

  1. Run go test -run TestRunHubAndSpokeDelegatedExample -count=1 -v -timeout 300m from tests directory

Anything else


By submitting this issue, you agree to follow our Code of Conduct

@imprateeksh
Copy link
Member

Tried running this quite a few times but in my case it has not failed even once yet.
I am still trying to see if there is any other step involved to reproduce this. Sharing results from one of the runs- output_test.txt

@imprateeksh
Copy link
Member

Unable to reproduce the issue. Hence unassigning myself.

@imprateeksh imprateeksh removed their assignment Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 Something isn't working internal-synced
Projects
None yet
Development

No branches or pull requests

3 participants