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

Delete of dependent resource doesn't always honor ordering #20823

Closed
kilokahn opened this issue Mar 26, 2019 · 4 comments
Closed

Delete of dependent resource doesn't always honor ordering #20823

kilokahn opened this issue Mar 26, 2019 · 4 comments

Comments

@kilokahn
Copy link

Terraform Version

Terraform v0.11.7

Terraform Configuration Files

resource "oci_waas_certificate" "test_certificate" {
  #Required
  certificate_data = ""
  compartment_id   = "${var.compartment_ocid}"
  private_key_data = ""

  #Optional
  display_name                   = "${var.certificate_display_name}"
  is_trust_verification_disabled = true
}

resource "oci_waas_waas_policy" "test_waas_policy" {
  #Required
  compartment_id = "${var.compartment_ocid}"
  domain         = "somethingnew42.oracle.com"

  policy_config {
    #Optional
    certificate_id   = "${oci_waas_certificate.test_certificate.id}"
    is_https_enabled = true
    is_https_forced  = true
  }
}

Debug Output

https://gist.github.com/kilokahn/12bd576727b59842154eb790504d04ba

Expected Behavior

oci_waas_waas_policy.test_waas_policy should be destroyed before
oci_waas_certificate.test_certificate

Actual Behavior

Both oci_waas_waas_policy.test_waas_policy and oci_waas_certificate.test_certificate were being destroyed simultaneously

Steps to Reproduce

We are going to put the acceptance test where we see this behavior on our github repo soon, and you can run that to see the problem in action.

Additional Context

We haven't seen this problem (yet) when running with a standalone .tf file. Tagging @paultyng for this

References

#20196 may be related to this.

@danieldreier
Copy link
Contributor

@kilokahn thank you for this issue report. We're aware of a variety of delete ordering issues, and would like to investigate and fix them. This specific issue report doesn't include reproduction steps, so there isn't a clear next step. Are you still planning on posting steps to reproduce? We're unable to investigate further without reproduction steps.

@danieldreier
Copy link
Contributor

@kilokahn I'm just reviewing this ahead of our meeting, and wanted to check if you've had time to put together a reproduction case, or to verify whether this is still happening in the current terraform release. Please let me know if there's any help we can provide to come up with a reproduction case.

@mildwonkey
Copy link
Contributor

I am going to close this issue due to inactivity.

If there is still a question, I recommend the the community forum, where there are far more people available to help. If there is a bug or you would like to make a feature request, please open a new issue and fill out the template.
Thanks!

@ghost
Copy link

ghost commented Oct 13, 2020

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.

@ghost ghost locked as resolved and limited conversation to collaborators Oct 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants