-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Changes found in EBS Block device where there aren't really changes #4786
Comments
Hi @davedash. I had the same problem.
|
Okay… this makes sense. But I feel this is different than before, since almost all of my volumes use a root abs volume. Does this behavior change based on instance size? This happens to be my t2.small that trigger this. -- On January 24, 2016 at 5:40:56 AM, Kazuma Watanabe ([email protected]) wrote: Hi @davedash. I had the same problem. ebs_block_device is additional block device. If you want to use it, specify root_block_device — |
Sorry, I don't know condition that not happened this problem...
If you want to know about that, you should ask in AWS developer forum. https://forums.aws.amazon.com/tags/ec2?categoryID=9 |
I am seeing this too. But it is not related to root_block_device. In my case (and I suspect the OP's too) it is caused by an aws_volume_attachment to the same instance. Whenever Terraform refreshes it adds the volume attached with the aws_volume_attachment to ebs_block_device.4278008646.* in the state file. When creating the plan it wants to remove this device as there is no ebs_block_device definition for it. |
I am seeing this also, like OP i have
|
Even with
I still get issues:
|
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. |
I keep seeing this on a few instances.
apply
keeps recreating the instances and then they instances still do the above. These are ont2.small
instances in EC2.Here's the original
tf
:The text was updated successfully, but these errors were encountered: