Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-110722

Unregistering via rhc results in failed systemd units

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-9.6, rhel-10.0
    • None
    • No
    • None
    • subs-client-tools
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      `rhc disconnect`

      I recognize that RHCCC is setup in a way that only expects you to individually use the provided services directly, and the units shipped with RHCCC also directly target those services. It makes sense however for someone to use `rhc` if they know about it or understand how it works, as it simplifies the process.

      Please provide the package NVR for which the bug is seen:

      redhat-cloud-client-configuration-cdn-1-15.el9.noarch

      How reproducible is this bug?: 100%

      Steps to reproduce

      1. Allow automatic registration to occur via rhccc
      2. rhc disconnect
      3. systemctl status --failed --no-pager -l

      Expected results

      No failed units.

      Actual results

      [root@ip-10-31-51-213 ~]# systemctl status --failed --no-pager -l
      × insights-register.service - Automatically Register with Red Hat Insights
           Loaded: loaded (/usr/lib/systemd/system/insights-register.service; static)
           Active: failed (Result: exit-code) since Thu 2025-08-21 18:33:16 UTC; 6s ago
         Duration: 16.889s
             Docs: man:insights-client(8)
          Process: 4256 ExecStopPost=/bin/systemctl mask --now insights-register.path (code=exited, status=0/SUCCESS)
         Main PID: 3964 (code=exited, status=1/FAILURE)
              CPU: 5.095s
      
      Aug 21 18:32:59 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: Started Automatically Register with Red Hat Insights.
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4246]: This host is unregistered, please ensure that the system is registered with subscription-manager and then with insights-client.
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4246]: 1. Register with subscription-manager
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4246]: # subscription-manager register
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4246]: 2. Register with insights-client
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4246]: # insights-client --register
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: insights-register.service: Main process exited, code=exited, status=1/FAILURE
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com systemctl[4256]: Created symlink /etc/systemd/system/insights-register.path → /dev/null.
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: insights-register.service: Failed with result 'exit-code'.
      Aug 21 18:33:16 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: insights-register.service: Consumed 5.095s CPU time.
      
      × insights-unregister.service - Automatically Unregister from Red Hat Insights
           Loaded: loaded (/usr/lib/systemd/system/insights-unregister.service; static)
           Active: failed (Result: exit-code) since Thu 2025-08-21 18:33:06 UTC; 16s ago
         Duration: 5.567s
      TriggeredBy: ● insights-unregister.path
             Docs: man:insights-client(8)
         Main PID: 4036 (code=exited, status=1/FAILURE)
              CPU: 5.022s
      
      Aug 21 18:33:00 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: Started Automatically Unregister from Red Hat Insights.
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4183]: This host is unregistered, please ensure that the system is registered with subscription-manager and then with insights-client.
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4183]: 1. Register with subscription-manager
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4183]: # subscription-manager register
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4183]: 2. Register with insights-client
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com insights-client[4183]: # insights-client --register
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: insights-unregister.service: Main process exited, code=exited, status=1/FAILURE
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: insights-unregister.service: Failed with result 'exit-code'.
      Aug 21 18:33:06 ip-10-31-51-213.us-east-1.aws.redhat.com systemd[1]: insights-unregister.service: Consumed 5.022s CPU time.

              csi-client-tools-bugs CSI Client Tools Bugs Bot
              rhn-support-cdonnell Craig Donnelly
              CSI Client Tools Bugs Bot CSI Client Tools Bugs Bot
              CSI Client Tools Bugs Bot CSI Client Tools Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: