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
Describe the bug
global_pool module is not handling the situation when pool exist, it still tries to create which makes the operation fail.
Also the module does not check the execution status and return success even through exectuin status shows failed.
Expected behavior
When IP pool already exist then if the parameters are changed then update should be tried in place of POST. Also the execution status should be check for correct status.
/dna/intent/api/v1/dnacaap/management/execution-status/228c6c0c-d252-433a-a9d2-91f6392b56ca
{
"bapiKey": "f793-192a-43da-bed9",
"bapiName": "Create Global Pool",
"bapiExecutionId": "228c6c0c-d252-433a-a9d2-91f6392b56ca",
"startTime": "Sun Nov 19 12:39:36 UTC 2023",
"startTimeEpoch": 1700397576741,
"endTime": "Sun Nov 19 12:39:37 UTC 2023",
"endTimeEpoch": 1700397577248,
"timeDuration": 507,
"status": "FAILURE",
"bapiError": "{"status":false,"errorMessage":[{"ippool":["NCIP10251: A pool named Fabric_VN already exists, which conflicts with the proposed global pool. for ip pool name Fabric_VN."]}]}",
"runtimeInstanceId": "DNACP_Runtime_24b23bf2-e056-452c-b1ad-beaee0b91e4c"
}
Environment (please complete the following information):
Cisco DNA Center Version and patch: 2.3.5.3
Ansible Version:
Collection version: 6.8.0
OS Version:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Prerequisites
Describe the bug
global_pool module is not handling the situation when pool exist, it still tries to create which makes the operation fail.
Also the module does not check the execution status and return success even through exectuin status shows failed.
Expected behavior
When IP pool already exist then if the parameters are changed then update should be tried in place of POST. Also the execution status should be check for correct status.
Screenshots
"item": {
"IpAddressSpace": "IPv4",
"dhcpServerIps": [
"204.192.3.40"
],
"dnsServerIps": [
"171.70.168.183"
],
"gateway": "204.1.32.1",
"ipPoolCidr": "204.1.32.0/20",
"ipPoolName": "EXT_POOL",
"type": "Generic"
},
"result": "Object already present"
}
changed: [dnaccluster14] => (item={'IpAddressSpace': 'IPv4', 'dhcpServerIps': ['204.192.3.40'], 'dnsServerIps': ['171.70.168.183'], 'gateway': '40.10.0.1', 'ipPoolCidr': '40.10.0.0/16', 'ipPoolName': 'Fabric_VN', 'type': 'Generic'}) => {
"ansible_loop_var": "item",
"changed": true,
"dnac_response": {
"executionId": "228c6c0c-d252-433a-a9d2-91f6392b56ca",
"executionStatusUrl": "/dna/platform/management/business-api/v1/execution-status/228c6c0c-d252-433a-a9d2-91f6392b56ca",
"message": "The request has been accepted for execution"
},
"item": {
"IpAddressSpace": "IPv4",
"dhcpServerIps": [
"204.192.3.40"
],
"dnsServerIps": [
"171.70.168.183"
],
"gateway": "40.10.0.1",
"ipPoolCidr": "40.10.0.0/16",
"ipPoolName": "Fabric_VN",
"type": "Generic"
},
"result": "Object created"
}
/dna/intent/api/v1/dnacaap/management/execution-status/228c6c0c-d252-433a-a9d2-91f6392b56ca
{
"bapiKey": "f793-192a-43da-bed9",
"bapiName": "Create Global Pool",
"bapiExecutionId": "228c6c0c-d252-433a-a9d2-91f6392b56ca",
"startTime": "Sun Nov 19 12:39:36 UTC 2023",
"startTimeEpoch": 1700397576741,
"endTime": "Sun Nov 19 12:39:37 UTC 2023",
"endTimeEpoch": 1700397577248,
"timeDuration": 507,
"status": "FAILURE",
"bapiError": "{"status":false,"errorMessage":[{"ippool":["NCIP10251: A pool named Fabric_VN already exists, which conflicts with the proposed global pool. for ip pool name Fabric_VN."]}]}",
"runtimeInstanceId": "DNACP_Runtime_24b23bf2-e056-452c-b1ad-beaee0b91e4c"
}
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: