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

Terraform timed out while applying updates to Triton Machine Metadata #6148

Closed
sodre opened this issue Apr 13, 2016 · 2 comments
Closed

Terraform timed out while applying updates to Triton Machine Metadata #6148

sodre opened this issue Apr 13, 2016 · 2 comments

Comments

@sodre
Copy link
Contributor

sodre commented Apr 13, 2016

Terraform Version

Terraform v0.6.15-dev (70c65fb+CHANGES)

Affected Resource(s)

triton_machine

Terraform Configuration Files

The Initial configuration is:

resource "triton_machine" "test" {
  name = "test"
  package = "t4-standard-128M"
  image = "eb9fc1ea-e19a-11e5-bb27-8b954d8c125c"
}

Then add a metadata field to the config file:

resource "triton_machine" "test" {
  name = "%s"
  package = "t4-standard-128M"
  image = "eb9fc1ea-e19a-11e5-bb27-8b954d8c125c"
  user_data = "hello"
}

Debug Output


Expected Behavior

Create/Update/Delete operations on Triton instances should return immediately after they are confirmed with the provider.

Actual Behavior

After calling terraform apply the second time the program times out.

Steps to Reproduce

Please list the steps requires to reproduce the issue, for example:

  1. Start with the basic instance config
  2. terraform apply
  3. Edit the config file and add the user_data field.
  4. terraform apply
    4.a) It will time out. <--- This is the bug
  5. terraform show | grep user_data
    5.b) user_data = "hello" as expected, that is the provider accepted the command.

Important Factoids

Running on debug install of Triton.

References

@sodre sodre changed the title Terraform fails to detect "convergence" of Triton Metadata Updates Terraform hangs while applying updates to Triton Machine Metadata Apr 13, 2016
@sodre sodre changed the title Terraform hangs while applying updates to Triton Machine Metadata Terraform timed out while applying updates to Triton Machine Metadata Apr 13, 2016
@stack72
Copy link
Contributor

stack72 commented Apr 13, 2016

Hi @sodre

I am going to close this out as you have opened a PR that fixes this work. Thanks so much for all the work on tracking this down and fixing it :)

Paul

@stack72 stack72 closed this as completed Apr 13, 2016
stack72 pushed a commit that referenced this issue Apr 20, 2016
* Add Triton Metadata modification AccTest.

The test starts the basic machine and then adds the metadata field
user_data.
Test fails if the user_data field does not match what we expect
OR it times out.

Related to #6148

* Fix the non-convergence of Triton metadata changes

The code waiting for the entire Machine Metadata to "deep equal" the Terraform
metadata modifications. These two sets will only be the same if the user
changes all metadata fields of the resource before calling `apply`.

Closes #6148
grubernaut pushed a commit to TritonDataCenter/terraform-provider-triton that referenced this issue Jun 6, 2017
* Add Triton Metadata modification AccTest.

The test starts the basic machine and then adds the metadata field
user_data.
Test fails if the user_data field does not match what we expect
OR it times out.

Related to hashicorp/terraform#6148

* Fix the non-convergence of Triton metadata changes

The code waiting for the entire Machine Metadata to "deep equal" the Terraform
metadata modifications. These two sets will only be the same if the user
changes all metadata fields of the resource before calling `apply`.

Closes hashicorp/terraform#6148
@ghost
Copy link

ghost commented Apr 26, 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 and limited conversation to collaborators Apr 26, 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

2 participants