# Facing Issue Ansible Summary

**URL:** <https://forum.ansible.com/t/facing-issue-ansible-summary/36134>\
**Category:** Ansible Project\
**Created:** [December 20, 2021, 2:34pm UTC](https://forum.ansible.com/t/facing-issue-ansible-summary/36134 "2021-12-20T14:34:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jitender\_J](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@Jitender\_J](https://forum.ansible.com/u/Jitender_J)\
**Post date:** [December 20, 2021, 2:34pm UTC](https://forum.ansible.com/t/facing-issue-ansible-summary/36134/1 "2021-12-20T14:34:02Z")

</div>

Hi Team,

Facing a very strange issue, my failed task output getting swapped with another task, in summary, we have done some modification in the callback module but never saw like this before, any suggestion

 ![tt.PNG](https://us1.discourse-cdn.com/ansible/original/2X/2/2b752f53b87e71ce163e5f22a23f1b232f6e9478.png)

---

<div class="post-metadata">

**Author:** ![Antony\_Stone](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@Antony\_Stone](https://forum.ansible.com/u/Antony_Stone)\
**Post date:** [December 20, 2021, 2:36pm UTC](https://forum.ansible.com/t/facing-issue-ansible-summary/36134/2 "2021-12-20T14:36:37Z")

</div>

My suggestion is to show us your playbook which can do this.

Antony.

---

<div class="post-metadata">

**Author:** ![Jitender\_J](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@Jitender\_J](https://forum.ansible.com/u/Jitender_J)\
**Post date:** [December 20, 2021, 2:44pm UTC](https://forum.ansible.com/t/facing-issue-ansible-summary/36134/3 "2021-12-20T14:44:36Z")

</div>

Hi Antony,

Thanks for the mail, below is the playbook code snippet

---

<div class="post-metadata">

**Author:** ![racke](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/racke/32/4767_2.png) [@racke](https://forum.ansible.com/u/racke)\
**Post date:** [December 20, 2021, 2:58pm UTC](https://forum.ansible.com/t/facing-issue-ansible-summary/36134/4 "2021-12-20T14:58:39Z")

</div>

> Hi Antony,
> 
> Thanks for the mail, below is the playbook code snippet
> 
> ##############################  
> - hosts: "{{ UI }}"  
> gather\_facts: no  
> user: ops  
> tasks:  
> - name: Check total CPU cores  
> shell: |  
> cpu=`sysctl hw.model hw.machine hw.ncpu|grep hw.ncpu:`  
> echo "$cpu"|awk -F':' '{  
> if ($2 \>= 5)  
> print "\033[32mOK:\033[0m" $0;  
> else  
> print $0, echo -e "\033[31m CRITICAL\033[0m" }'  
> register: err\_cpu  
> failed\_when: '"CRITICAL" in err\_cpu.stdout'  
> args:  
> executable: /bin/bash  
> ignore\_errors: true
> 
> ```
> \- name: Check total memory
> shell: |
> mem=\`echo &quot;$\(sysctl \-n hw\.physmem\)/1024/1024/1024&quot;|bc\`
> echo &quot;$mem&quot;|awk &#39;\{
> if \($NF &gt;= 48\)
> print &quot;\\033\[32mOK:\\033\[0m&quot; $0
> else
> print $0, echo \-e &quot;\\033\[31m CRITICAL\\033\[0m&quot; \}&#39;
> register: err\_mem
> failed\_when: &#39;&quot;CRITICAL&quot; in err\_mem\.stdout&#39;
> args:
> executable: /bin/bash
> ignore\_errors: true
> 
> ```
> 
> #############################

Why don't use ansible\_facts instead of these horrible shell hacks?

Regards  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Racke