Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1833408

Summary: [RHEL6]insights-client daily cron trigger mails to root on everyday execution
Product: Red Hat Hybrid Cloud Console (console.redhat.com) Reporter: Amar Huchchanavar <ahuchcha>
Component: ClientAssignee: jcrafts
Status: CLOSED DUPLICATE QA Contact: Pavol Kotvan <pakotvan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: klape, link, lphiri
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-11 11:27:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amar Huchchanavar 2020-05-08 15:38:49 UTC
Description of problem:
Code change introduced in insights-client-3.0.13-1.el6_10.noarch trigger emails to root on everyday execution.
~~~
Example:
From: Anacron <root.com>
To: root.com
Subject: Anacron job 'cron.daily' on client.example.com
Date: Tue, 21 Apr 2020 19:06:46 +0530 (IST)
Status: RO

/etc/cron.daily/insights-client:

Sleeping for 6801 seconds
~~~

Version-Release number of selected component (if applicable):
Package insights-client.noarch 0:3.0.13-1.el6_10 will be an update

How reproducible:
Always

Steps to Reproduce:
1.Install RHEL 6.10
2.Install pkg: insights-client.noarch 0:3.0.13-1.el6_10 
3.insights-client --register 
4.Wait for the anacron exection or #run-parts /etc/cron.daily/ (sometimes this does not generate mail)

Actual results:
The root mailbox is flooded with Anacron Insights messages.

Expected results:
Avoid sending mail

Additional info:
It appears that the newly added code causing the issue.

echo "Sleeping for ${DELAY} seconds"
/bin/sleep ${DELAY}

Comment 3 Link Dupont 2020-05-11 11:27:01 UTC

*** This bug has been marked as a duplicate of bug 1828778 ***