Bug 2062153

Summary: insights-client-results.path triggers endlessly
Product: Red Hat Enterprise Linux 9 Reporter: Marius Vollmer <mvollmer>
Component: insights-clientAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: Pavol Kotvan <pakotvan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: cmarinea, fjansen, gchamoul, link, stomsa
Target Milestone: rc   
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: 2022-03-09 13:42:36 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 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