RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2062153 - insights-client-results.path triggers endlessly
Summary: insights-client-results.path triggers endlessly
Keywords:
Status: CLOSED DUPLICATE of bug 2022191
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: insights-client
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nobody
QA Contact: Pavol Kotvan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-09 10:08 UTC by Marius Vollmer
Modified: 2023-09-15 01:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-09 13:42:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-114921 0 None None None 2022-03-09 10:17:34 UTC

Description Marius Vollmer 2022-03-09 10:08:48 UTC 
Description of problem:

Starting insights-client-results.path results in a avalanche of insights-client-results.service starts, until systemd fails the units with "start-limit-hit".

Version-Release number of selected component (if applicable):
insights-client-3.1.7-1.el9.noarch

How reproducible:
Always

Steps to Reproduce:
1. insights-client --register
2. Wait a few minutes, maybe watch journalctl -f until things calm down
3. systemctl status insights-client-results.path
4. systemctl reset-failed
5. systemctl start insights-client-results.path
6. Watch it spin up again and eventually fail with start-limit-hit

Actual results:
× insights-client-results.path - Monitor /etc/insights-client/.lastupload for modifications
     Loaded: loaded (/usr/lib/systemd/system/insights-client-results.path; enabled; vendor preset: disabled)
     Active: failed (Result: unit-start-limit-hit) since Wed 2022-03-09 04:58:14 EST; 4min 1s ago
   Triggers: ● insights-client-results.service
       Docs: man:insights-client(8)


Expected results:
insights-client-results.service runs only once for every change of .lastupload.

Additional info:
This is caused by using PathExists=, I think. PathChanged= should be all that is needed, even PathModified= is too much.
Comment 2 Red Hat Bugzilla 2023-09-15 01:22:40 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.