You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
oci_core_instance_configuration.lb_sample: Still destroying... [id=ocid1.instanceconfiguration.oc1.iad.aaa...wn2ta4acmlpjtq2svx3udecqknvafndfqw6vma, 1m40s elapsed]
oci_core_instance_configuration.lb_sample: Still destroying... [id=ocid1.instanceconfiguration.oc1.iad.aaa...wn2ta4acmlpjtq2svx3udecqknvafndfqw6vma, 1m50s elapsed]
oci_core_instance_configuration.lb_sample: Still destroying... [id=ocid1.instanceconfiguration.oc1.iad.aaa...wn2ta4acmlpjtq2svx3udecqknvafndfqw6vma, 2m0s elapsed]
Error: Service error:Conflict. The Instance Configuration ocid1.instanceconfiguration.oc1.iad.aaaaaaaazlamlpjtq2svx3udecqknvafnuspyc4qhwv5wn2ta4acdfqw6vma is associated to one or more Instance Pools.. http status code: 409. Opc request id: ffbb0fb6bcf7d77670845661a2e6f7b8/94218E311A3FDC5E527827D641D6B41F/536AD2A18D6167FDD227561187330C42
Panic Output
Expected Behavior
When a script update requires destroy/create for existing oci_core_instance_configuration that is associated with existing oci_core_instance_pool instance, those oci_core_instance_pool instances should also be flagged to destroy/create
Actual Behavior
I modified the scripts which resulted in need to destroy/create oci_core_instance_configuration which is associated with an existing oci_core_instance_pool. The apply operation fails with message suggesting the destroy operation cannot complete because the oci_core_instance_configuration is associated with an oci_core_instance_pool
Steps to Reproduce
Create script for resource oci_core_instance.sample to use as basis for script sample above
terraform apply to build instance configuration, instance pool
terraform taint oci_core_instance.sample then terraform apply to rebuild oci_core_instance
This causes oci_core_instance_configuration.sample to destroy/create as well but will fail during destroy because of reference to oci_core_instance_pool
Important Factoids
References
The text was updated successfully, but these errors were encountered:
This is done as per service documentation to allow instance pool with instances created from different instance configurations:
If you modify the instance configuration for an instance pool, existing instances that are part of that pool will not change. Any new instances created after the instance configuration change will use the new instance configuration. New instances will not be created unless you have increased the size of the instance pool or terminate existing instances.
The update (terraform apply) will fail in your scenario due to the following service requirement:
You can't delete an instance configuration if it is associated with at least one instance pool.
Community Note
Terraform Version and Provider Version
Terraform v0.12.21
Affected Resource(s)
oci_core_instance_configuration
oci_core_instance_pool
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
When a script update requires destroy/create for existing
oci_core_instance_configuration
that is associated with existingoci_core_instance_pool
instance, thoseoci_core_instance_pool
instances should also be flagged to destroy/createActual Behavior
I modified the scripts which resulted in need to destroy/create
oci_core_instance_configuration
which is associated with an existingoci_core_instance_pool
. Theapply
operation fails with message suggesting the destroy operation cannot complete because theoci_core_instance_configuration
is associated with anoci_core_instance_pool
Steps to Reproduce
oci_core_instance.sample
to use as basis for script sample aboveterraform apply
to build instance configuration, instance poolterraform taint oci_core_instance.sample
thenterraform apply
to rebuildoci_core_instance
oci_core_instance_configuration.sample
to destroy/create as well but will fail during destroy because of reference tooci_core_instance_pool
Important Factoids
References
The text was updated successfully, but these errors were encountered: