Observed behavior after upgrading Terraform provider from older version to ciscodevnet/catalystcenter 0.5.8.
Environment:
Cisco Catalyst Center SDA deployment
One fabric site contains multiple Edge Nodes (EN)
2 ENs are currently down/unreachable
Terraform resource:
catalystcenter_anycast_gateway
Issue:
Earlier provider versions appeared to continue with warnings when some devices in the site were unreachable. After upgrading to provider version 0.5.8, Terraform now fails completely during terraform apply.
Error returned:
Error: Client Error
Failed to configure object (POST), got error:
task '019e01dd-5ba3-79e3-9774-d494f07e56af' failed:
TASK_MODIFY_PUT, NCSP11017:
Operation failed on '2' devices.
"isError": true
Observations:
The failure corresponds to exactly 2 unreachable Edge Nodes in the SDA site
Catalyst Center task backend reports:
Determination of network intent deployment status
The Terraform provider now treats this as a hard failure and aborts the apply
Questions:
Was there a behavioral change in provider version 0.5.8 regarding async task error handling?
Did previous versions intentionally allow partial deployment success while only returning warnings?
Is there a recommended way to ignore/down-rank deployment failures for unreachable SDA Edge Nodes?
Is this expected behavior for catalystcenter_anycast_gateway resources when some fabric devices are offline?
Additional context:
The issue appears related to SDA intent deployment validation
Catalyst Center backend returns NCSP11017
Terraform fails even though only 2 devices in the site are affected
with module.sda_networks.catalystcenter_anycast_gateway.this["lab_1"],
on modules/sda_networks/main.tf line 40, in resource "catalystcenter_anycast_gateway" "this":
40: resource "catalystcenter_anycast_gateway" "this" {
Failed to configure object (POST), got error: task
'019e01dd-5ba3-79e3-9774-d494f07e56af' failed: TASK_MODIFY_PUT, NCSP11017:
Operation failed on '2' devices.,
{"response":{"endTime":1778147765831,"data":"workflow_id=0a0b8fb6-d1e8-40eb-9eb5-d7b08375bf91;cfs_id=9905eba7-b794-43e9-b322-7a29019ccd72;rollback_status=not_supported;rollback_taskid=0;failure_task=Determination
of network intent deployment
status:49ac6d77-11ca-44d8-b9fc-5c7c10dfc1b4;processcfs_complete=true","progress":"TASK_MODIFY_PUT","version":1778147765831,"startTime":1778147744675,"errorCode":"NCSP11017","lastUpdate":1778147765798,"serviceType":"NCSP","failureReason":"NCSP11017:
Operation failed on '2'
devices.","isError":true,"instanceTenantId":"6734a3da64c5e82aad45e1b2","id":"019e01dd-5ba3-79e3-9774-d494f07e56af"},"version":"1.0"}
Error: Client Error
with module.sda_networks.catalystcenter_anycast_gateway.this["lab_10"],
on modules/sda_networks/main.tf line 40, in resource "catalystcenter_anycast_gateway" "this":
40: resource "catalystcenter_anycast_gateway" "this" {
Failed to configure object (POST), got error: task
'019e01dd-af32-72c3-96dd-343a1a3968b4' failed: TASK_MODIFY_PUT, NCSP11017:
Operation failed on '2' devices.,
{"response":{"endTime":1778147785917,"data":"workflow_id=8526d980-c9ff-42b9-9af1-207be70078c4;cfs_id=9905eba7-b794-43e9-b322-7a29019ccd72;rollback_status=not_supported;rollback_taskid=0;failure_task=Determination
of network intent deployment
status:56725c05-36f6-4052-a032-0ce5fce758d8;processcfs_complete=true","progress":"TASK_MODIFY_PUT","version":1778147785917,"startTime":1778147766066,"errorCode":"NCSP11017","lastUpdate":1778147785885,"serviceType":"NCSP","failureReason":"NCSP11017:
Operation failed on '2'
devices.","isError":true,"instanceTenantId":"6734a3da64c5e82aad45e1b2","id":"019e01dd-af32-72c3-96dd-343a1a3968b4"},"version":"1.0"}
Observed behavior after upgrading Terraform provider from older version to ciscodevnet/catalystcenter 0.5.8.
Environment:
Cisco Catalyst Center SDA deployment
One fabric site contains multiple Edge Nodes (EN)
2 ENs are currently down/unreachable
Terraform resource:
catalystcenter_anycast_gateway
Issue:
Earlier provider versions appeared to continue with warnings when some devices in the site were unreachable. After upgrading to provider version 0.5.8, Terraform now fails completely during terraform apply.
Error returned:
Error: Client Error
Failed to configure object (POST), got error:
task '019e01dd-5ba3-79e3-9774-d494f07e56af' failed:
TASK_MODIFY_PUT, NCSP11017:
Operation failed on '2' devices.
"isError": true
Observations:
The failure corresponds to exactly 2 unreachable Edge Nodes in the SDA site
Catalyst Center task backend reports:
Determination of network intent deployment status
The Terraform provider now treats this as a hard failure and aborts the apply
Questions:
Was there a behavioral change in provider version 0.5.8 regarding async task error handling?
Did previous versions intentionally allow partial deployment success while only returning warnings?
Is there a recommended way to ignore/down-rank deployment failures for unreachable SDA Edge Nodes?
Is this expected behavior for catalystcenter_anycast_gateway resources when some fabric devices are offline?
Additional context:
The issue appears related to SDA intent deployment validation
Catalyst Center backend returns NCSP11017
Terraform fails even though only 2 devices in the site are affected