Thanks Niclas, sharing is caring. :)
---
Nux
www.nux.ro [1]
On 2022-08-03 18:04, Niclas Lindblom wrote:
And of course as soon as I posted this I realised my own stupidity, but
I thought I share it.
I store some static key pair values in Consul that are retrieved by the
Consul Terraform module where there was a case sensitivity mismatch
Large Instance (Cloudstack) was retrieved as Large instance from the
key store triggering the Terraform change
However
disk_offering I had as "custom" which is what the documentation states,
but should be "Custom" for Terraform to match and not trigger a disk
change
Niclas
On 3 Aug 2022, at 18:46, Niclas Lindblom
<[email protected]> wrote:
Hello,
I am not sure if the Cloudstack Terraform module is community
supported through this forum, but I have an issue which I am not sure
if it is with the module or with Terraform itself. When I deploy a
virtual machine and create/attach a disk it works fine on the first
run and the resources are created. However, when I run Terraform again
without any code changes, Terraform detects that the resources needs
to be upgraded (which isn't the case) and then fails with the message
in my case:
Error changing the service offering for instance
VM-c3a9b229-f817-47ea-8f8b-99fe13dbf003: CloudStack API error 431
(CSExceptionErrorCode: 4350): Not upgrading vm VM instance {id: "64",
name: "i-2-64-VM", uuid: "c3a9b229-f817-47ea-8f8b-99fe13dbf003",
type="User"} since it already has the requested service offering
(Large Instance)
Has anyone seen this before and have any advise to offer ?
Terraform version: 1.2.6
Cloudstack version: 4.17.0
Terraform Cloudstack Module: 0.4.0
Regards
Niclas
Links:
------
[1] http://www.nux.ro
