Details
-
Type: Bug
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.5
-
Epic Link:
-
Sprint:Spring 6 : 30 Mar to Apr 10
Description
Running the playbooks from newly provisioned ansible control node produced the attached error.
For this task, please review error report and investigate why the error has occurred. Add a note here indicating the cause and potential fix. (For example, the problem could be a misconfiguration of the control node.)
Attachments
Issue Links
- relates to
-
IGBF-2314 Investigate: Can ansible plugins help us to solve appstore-playbook bug reported in IGBF-2311?
- Closed
This was not an error as such. Somewhere in the text was a message "msg": "Aborting since identical entry of instance has been found" .....It was a forced failure to create a new EC2 since we dont create 2 EC2 instances with the same name.
I went and tried some changes to remove the clutter of messages that make it hard to spot the error.
Below config changes will do the following
Improve the output of ansible executions is still in progress
Below Config change is needed to be added to file /etc/ansible/ansible.cfg.
display_skipped_hosts = no
stdout_callback = yaml