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
When attempting config-driven import of existing infrastructure into tfstate for catalystcenter_global_pool objects, terraform fails with error.
│Error: Cannot import non-existent remote object
│
│ While attempting to import an existing object to "catalystcenter_global_pool.this[\"glob_etu_3_v666_1\"]", the provider detected that no object exists with the given id. Only pre-existing objects can be imported; check that the id is correct and that it is associated with the provider's configured region or endpoint, or use
│ "terraform apply" to create a new remote object for this resource.
It is not clear from documentation what "id=string" is, but debuglogs does not show any attempt of any read-operation regardless of what id we specify. The following is from debug logs:
2024-09-24T15:11:14.869+0200 [DEBUG] ReferenceTransformer: "catalystcenter_ip_pool.this[\"glob_etu_3_v666_1\"]" references: []
2024-09-24T15:11:15.187+0200 [DEBUG] Resource instance state not found for node "catalystcenter_global_pool.this[\"glob_etu_3_v666_1\"]", instance catalystcenter_global_pool.this["glob_etu_3_v666_1"]
Manual API GET response is ok for the global pools, and the pools exist in catalystCenter (example http get response below)
Config-driven import is essential to be able to migrate from the older dnacenter-provider to the new catalystcenter-provider as these resources cannot be destroyed/recreated in production environments.
Cisco Catalyst Center version and patch: 2.3.7.6-70319
Terraform version: 1.9.5
Cisco Catalyst Center provider version: 1.0.0-beta
OS Version: Ubnutu 22.04
The text was updated successfully, but these errors were encountered:
When attempting config-driven import of existing infrastructure into tfstate for catalystcenter_global_pool objects, terraform fails with error.
Example of import:
Our tfvars:
It is not clear from documentation what "id=string" is, but debuglogs does not show any attempt of any read-operation regardless of what id we specify. The following is from debug logs:
Manual API GET response is ok for the global pools, and the pools exist in catalystCenter (example http get response below)
Config-driven import is essential to be able to migrate from the older dnacenter-provider to the new catalystcenter-provider as these resources cannot be destroyed/recreated in production environments.
The text was updated successfully, but these errors were encountered: