Bug 2027263

Summary:

insights-client-results.service keeps active after SM auto registered in aws

Product:

Red Hat Enterprise Linux 9

Reporter:

Frank Liang <xiliang>

Component:

insights-client

Assignee:

Nobody <nobody>

Status:

CLOSED DUPLICATE

QA Contact:

Pavol Kotvan <pakotvan>

Severity:

high

Docs Contact:

Priority:

high

Version:

9.0

CC:

cdonnell, cmarinea, fjansen, gchamoul, linl, mhayden, redakkan, ribarry, vkuznets, ymao

Target Milestone:

Keywords:

Triaged

Target Release:

---

Flags:

pm-rhel: mirror+

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2022-02-01 15:00:00 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:

Bug Depends On:

Bug Blocks:

2022191, 2055036, 2061967, 2070323, 2109244

Attachments:

Description	Flags
os_tests.tests.test_lifecycle.TestLifeCycle.test_boot_debugkernel.debug	none

Description Frank Liang 2021-11-29 09:10:21 UTC

Created attachment 1843970 [details]
os_tests.tests.test_lifecycle.TestLifeCycle.test_boot_debugkernel.debug

Description of problem:
After system SM auto registered in aws, the system bootup cannot finish successfully because of insights-client-results.service keeping in active.

[root@ip-10-116-2-58 insights-client]# systemd-analyze blame
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
[root@ip-10-116-2-58 insights-client]# systemctl list-jobs
JOB    UNIT                            TYPE  STATE  
129410 insights-client-results.service start running

1 jobs listed.
[root@ip-10-116-2-58 insights-client]# uname -r
5.14.0-1.7.1.el9.aarch64
[root@ip-10-116-2-58 insights-client]# rpm -q insights-client
insights-client-3.1.6-2.el9.noarch
[root@ip-10-116-2-58 insights-client]# systemctl status insights-client-results.service
● insights-client-results.service - Check for insights from Red Hat Cloud Services
     Loaded: loaded (/usr/lib/systemd/system/insights-client-results.service; static)
     Active: activating (start) since Mon 2021-11-29 08:50:20 UTC; 823ms ago
TriggeredBy: ● insights-client-results.path
       Docs: man:insights-client(8)
   Main PID: 75996 (insights-client)
      Tasks: 2 (limit: 46872)
     Memory: 20.3M
        CPU: 823ms
     CGroup: /system.slice/insights-client-results.service
             ├─75996 /usr/libexec/platform-python /usr/bin/insights-client --check-results
             └─76002 /usr/libexec/platform-python -c "from insights.client import InsightsClient; print(InsightsClient(None, False).version())"

Nov 29 08:50:20 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Starting Check for insights from Red Hat Cloud Services...
[root@ip-10-116-2-58 insights-client]# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Disabled
Content Access Mode is set to Simple Content Access. This host has access to content, regardless of subscription status.

System Purpose Status: Disabled

[root@ip-10-116-2-58 insights-client]# insights-client --status
System is registered locally via .registered file. Registered at 2021-11-29T06:24:18.121773
Insights API confirms registration.

There are tons of message produced:
[root@ip-10-116-2-58 insights-client]# journalctl -u insights-client-results.service
-- Journal begins at Mon 2021-11-29 06:34:39 UTC, ends at Mon 2021-11-29 09:03:31 UTC. --
Nov 29 06:34:45 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Starting Check for insights from Red Hat Cloud Services...
Nov 29 06:34:52 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: insights-client-results.service: Deactivated successfully.
Nov 29 06:34:52 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Finished Check for insights from Red Hat Cloud Services.
Nov 29 06:34:52 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: insights-client-results.service: Consumed 4.161s CPU time.
Nov 29 06:34:52 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Starting Check for insights from Red Hat Cloud Services...
Nov 29 06:35:25 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: insights-client-results.service: Deactivated successfully.
Nov 29 06:35:25 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Finished Check for insights from Red Hat Cloud Services.
Nov 29 06:35:25 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: insights-client-results.service: Consumed 4.162s CPU time.
Nov 29 06:35:25 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Starting Check for insights from Red Hat Cloud Services...
Nov 29 06:35:30 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: insights-client-results.service: Deactivated successfully.
Nov 29 06:35:30 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: Finished Check for insights from Red Hat Cloud Services.
Nov 29 06:35:30 ip-10-116-2-58.us-west-2.compute.internal systemd[1]: insights-client-results.service: Consumed 4.187s CPU time.
......
......

RHEL Version:
RHEL-9.0(5.14.0-1.7.1.el9.aarch64)

How reproducible:
100%

Steps to Reproduce:
1. start a rhel-9 beta t4g.large instance
2. check the boot time

Actual results:
system cannot finish bootup successfully.

Expected results:
system bootup can finish normally

Additional info:
- N/A

Comment 3 Gaël Chamoulaud 2022-02-01 13:59:16 UTC

That issue will certainly be fixed with insights-client-3.1.7-3.el9

Comment 4 Gaël Chamoulaud 2022-02-01 15:00:00 UTC


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