Describe the bug
When running a play with module 'cisco.ise.egress_matrix_cell' to create a CTS egress matrix cell for the first time, the play completes and the configuration change is successful.
When running the same play a subsequent time, the playbook fails with a 400 error such as:
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: }
fatal: [ise32-3.ise.trappedunderise.com]: FAILED! => {"changed": false, "msg": "An error occured when executing operation. The error was: [400] - Operation Egress Policy Matrix Create failed: Error : Cell Already Exsits !\n MATRIX_CELL failed. Look at the debug logs for more information\n{\n \"ERSResponse\" : {\n \"operation\" : \"POST-create-egressmatrixcell\",\n \"messages\" : [ {\n \"title\" : \"Operation Egress Policy Matrix Create failed: Error : Cell Already Exsits !\n MATRIX_CELL failed. Look at the debug logs for more information\",\n \"type\" : \"ERROR\",\n \"code\" : \"CRUD operation exception\"\n } ],\n \"link\" : {\n \"rel\" : \"related\",\n \"href\" : \"https://ise32-3.ise.trappedunderise.com/ers/config/egressmatrixcell\",\n \"type\" : \"application/xml\"\n }\n }\n}"}
Expected behavior
The expected behaviour would be that the module recognises that the configuration already exists and skip the attempt to create the object again.
Environment (please complete the following information):
Prerequisites
Describe the bug When running a play with module 'cisco.ise.egress_matrix_cell' to create a CTS egress matrix cell for the first time, the play completes and the configuration change is successful. When running the same play a subsequent time, the playbook fails with a 400 error such as:
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: } fatal: [ise32-3.ise.trappedunderise.com]: FAILED! => {"changed": false, "msg": "An error occured when executing operation. The error was: [400] - Operation Egress Policy Matrix Create failed: Error : Cell Already Exsits !\n MATRIX_CELL failed. Look at the debug logs for more information\n{\n \"ERSResponse\" : {\n \"operation\" : \"POST-create-egressmatrixcell\",\n \"messages\" : [ {\n \"title\" : \"Operation Egress Policy Matrix Create failed: Error : Cell Already Exsits !\n MATRIX_CELL failed. Look at the debug logs for more information\",\n \"type\" : \"ERROR\",\n \"code\" : \"CRUD operation exception\"\n } ],\n \"link\" : {\n \"rel\" : \"related\",\n \"href\" : \"https://ise32-3.ise.trappedunderise.com/ers/config/egressmatrixcell\",\n \"type\" : \"application/xml\"\n }\n }\n}"}
Expected behavior The expected behaviour would be that the module recognises that the configuration already exists and skip the attempt to create the object again.
Environment (please complete the following information):
Ansible Playbook Code Example
The previous plays execute without error when running multiple times, so the following modules exhibit the expected behaviour.