Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
While installing insights-client, rpm prints out
Failed to preset unit: Unit file insights-register.path does not exist.
Failed to preset unit: Unit file insights-unregister.path does not exist.
Failed to preset unit: Unit file 80-insights.preset.service does not exist.
This is likely caused by the
postinstall scriptlet (using /bin/sh):
if [ $1 -eq 1 ] && [ -x /usr/bin/systemctl ]; then
# Initial installation
/usr/bin/systemctl --no-reload preset insights-register.path || :
fi
if [ $1 -eq 1 ] && [ -x /usr/bin/systemctl ]; then
# Initial installation
/usr/bin/systemctl --no-reload preset insights-unregister.path || :
fi
if [ $1 -eq 1 ] && [ -x /usr/bin/systemctl ]; then
# Initial installation
/usr/bin/systemctl --no-reload preset 80-insights.preset || :
fi
None of the first two unit files are installed by the RPM.
The third unit file (from what I understood from systemd manual) should not be used via "systemctl preset", but is instead a declarative file containing settings for what the presets should be for *other* unit files in regular locations.
Version-Release number of selected component (if applicable):
insights-client-3.1.7-1.el9.noarch
Description of problem: While installing insights-client, rpm prints out Failed to preset unit: Unit file insights-register.path does not exist. Failed to preset unit: Unit file insights-unregister.path does not exist. Failed to preset unit: Unit file 80-insights.preset.service does not exist. This is likely caused by the postinstall scriptlet (using /bin/sh): if [ $1 -eq 1 ] && [ -x /usr/bin/systemctl ]; then # Initial installation /usr/bin/systemctl --no-reload preset insights-register.path || : fi if [ $1 -eq 1 ] && [ -x /usr/bin/systemctl ]; then # Initial installation /usr/bin/systemctl --no-reload preset insights-unregister.path || : fi if [ $1 -eq 1 ] && [ -x /usr/bin/systemctl ]; then # Initial installation /usr/bin/systemctl --no-reload preset 80-insights.preset || : fi None of the first two unit files are installed by the RPM. The third unit file (from what I understood from systemd manual) should not be used via "systemctl preset", but is instead a declarative file containing settings for what the presets should be for *other* unit files in regular locations. Version-Release number of selected component (if applicable): insights-client-3.1.7-1.el9.noarch