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.
+++ This bug was initially created as a clone of Bug #1870186 +++
In AWS RHEL-8.3, it takes over 120s in each boot after registration. Seems it is because it sleeps 120 seconds in service configuration.
IMO, it is a rough way to wait a static seconds in service.
[ec2-user]# systemd-analyze
Startup finished in 5.175s (kernel) + 27.438s (initrd) + 2min 19.177s (userspace) = 2min 51.791s
multi-user.target reached after 14.437s in userspace
[ec2-user]# systemd-analyze blame
2min 5.997s insights-client-results.service
6.787s cloud-init-local.service
5.290s dracut-cmdline.service
4.384s dracut-initqueue.service
3.190s dracut-pre-udev.service
[ec2-user]# cat /usr/lib/systemd/system/insights-client-results.service
""""""
[Service]
Type=oneshot
RemainAfterExit=no
ExecStart=/usr/bin/sleep 120
ExecStart=/usr/bin/insights-client --check-results
Restart=no
""""""
# rpm -qa|grep insights
insights-client-3.1.0-2.el8.noarch
Version-Release number of selected components (if applicable):
RHEL Version:
RHEL-8.3(4.18.0-232.el8.x86_64)
How reproducible:
100%
Steps to Reproduce:
1. Start a RHEL8.3 t3a.small instance
2. Register the insights client and reboot
3. Check system boot time via "systemd-analyze"
Actual results:
This service takes over 120s in each boot
Expected results:
Do not wait so long.
Additional info:
- N/A
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (insights-client bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4797
Comment 12Red Hat Bugzilla
2023-09-14 06:05:57 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days