Error while applying an update

[pshail]

Error when scaling-up / adding new resource to an existing terraform inventory.

Basically was increasing the count of few resources and it gives the following error.

• openstack_compute_instance_v2.control.0: diffs didn't match during apply. This is a bug with Terraform and should be reported.
• openstack_compute_instance_v2.worker.0: diffs didn't match during apply. This is a bug with Terraform and should be reported.

[phinze]

Hi @heckdevice, we can definitely help look into this, can you share a bit more detail about the config / state when you encountered this error.

If we can come up with steps to reproduce the error, we can figure out what the bug is and get it fixed! 👍

[pshail]

Basically was trying to update a deployment of two nodes to three nodes and each node have a floating ip association. This is on a in-house OpenStack setup.

On applying the update the above error comes.

[jtopjian]

@heckdevice Are you able to post the Terraform configuration you're using to trigger this?

Off the top of my head, if you're using count and something like element, this may be a result of #3449.

[pshail]

@jtopjian i am relying on the count for increasing the count but have no volume mapping as its managed by nova and not cinder in my openstack. I however am associating floating ips to each instance.

PFA the terraform file that i first apply
dc1-base.txt

on update i am simply changing the datanode_count. The plan goes through but on applying this change the issue is revealed.

[jtopjian]

OK, sounds very similar to #3662 (which is another symptom of #3449). Can you confirm if #3662 looks more similar to what you're seeing? If not, I'll try to reproduce this issue on my end.

[pshail]

@jtopjian Looking into #3449 it seems more like #3885

[jtopjian]

OK, good to know. I think it's safe to say the problem you're seeing is a bug in core. Someone in #3449 mentioned a workaround -- maybe that can get things sorted for the time being?

Let me know your thoughts. If you're getting confident that the problem you're seeing can be compared to one of the other issues that point to #3449, I'll close this issue in favor of #3449.

[pshail]

@jtopjian Let's close for now in fav of #3449. Will check back on the workaround if it actually works. Thanks.

[jtopjian]

@heckdevice okie dokie

[ghost]

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.