-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cisco.ise.egress_matrix_cell module returns 400 error if cell already exists #108
Comments
Please provide us collection Debug |
Debug output for the failed task...
|
Hi @grg1bbs, reviewing the issue note the following: And since the name of your playbook is different from those brought by the get_all, the POST is executed, but at the internal level those parameters are already set causing the error: Cell Already Exists This is more of a fault of the lab that it does not bring more information, but if the get_by_id is done it does bring the complete information, but executing a get_by_id for each result of the get_all is not viable in terms of time and performance Also the problem that the name is different is an error/problem at the CiscoISE LAB level, because in the POST the name is ignored and another defect is put in by changing it |
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.
The text was updated successfully, but these errors were encountered: