-
Bug
-
Resolution: Unresolved
-
Blocker
-
6.18.1, 6.18.2
-
False
-
Proton Refinement Backlog
-
sat-proton
-
None
-
None
-
None
-
None
Description
On an IOP-enabled Satellite server, the insights-client registration on a client host that is registered to Satellite is getting automatically unregistered immediately after successful registration.
The registration command completes successfully, but insights-client --status shows that the system is not registered via the Insights API and becomes locally unregistered.
Environment
- Red Hat Satellite with IOP enabled
- Client system registered to Satellite
- Insights client installed on client system
Error Received:
# insights-client --register Successfully registered host client.example.com Automatic scheduling for Insights has been enabled. Starting to collect Insights data for client.example.com Writing RHSM facts to /etc/rhsm/facts/insights-client.facts ... Uploading Insights data. Successfully uploaded report for client.example.com. View the Red Hat Insights console at https://console.redhat.com/insights/ # insights-client --status System is registered locally via .registered file. Registered at 2026-01-22T13:42:18.846356 Insights API says this machine is NOT registered. System unregistered locally via .unregistered file
Steps Taken / Troubleshooting Performed
1: Run the following commands:
# insights-client --unregister # rm -fr /etc/insights-client/machine-id # insights-client --register
# insights-client --unregister # rm /etc/insights-client/machine-id # subscription-manager remove --all # subscription-manager unregister # subscription-manager clean # subscription-manager register # insights-client --register
2: Verified that all Satellite services are running.
3: Checked journalctl logs found iop-core-puptoo related errors in journal logs:
iop-core-puptoo[47311]: MainThread ERROR insights-puptoo - Failed to extract archive: (2, ['tar', '--delay-directory-restore', '-z', '-x', '--exclude=*/dev/*', '-f', '/tmp/tmpuwlu_of0', '-C', '/tmp/insights-4vu_fepw'], b'tar: insights-client.example.com-20260127130712/data/insights_commands/ls_-lH_.boot.grub.grub.conf_.boot.grub2.grub.cfg_.dev.mapper.vgdata-lvapp_.dev.mapper.vgdata-lvccv_.dev.mapper.vgdata-lvdata_.dev.mapper.vgdata-lvhome_.dev.mapper.vgdata-lvlogs_.dev.mapper.vgdata-lvopt_.dev.mapper.vgsystem-lvroot_.dev.mapper.vgsystem-lvsw: Cannot open: File name too long\\ntar: insights-client.example.com-20260127130712/data/insights_commands/ls_-lan_._.boot_.ccv_.dev_.dev.block_.dev.cciss_.dev.disk.by-id_.dev.disk.by-label_.dev.disk.by-path_.dev.disk.by-uuid_.dev.mapper_.dev.oracleasm.disks_.etc_.etc.crypto-policies_.etc.crypto-policies.back-ends_.etc.crypto-policies.state_.etc.dnf.vars_.etc.: Cannot open: File name too long\\ntar: Exiting with failure status due to previous errors\\n') Jan 27 13:07:42 client.example.com iop-core-puptoo[47311]: MainThread ERROR insights-puptoo - Failed to process message of advisor service: a7dc4202acccca5020a0c88b1462b139: ('process_archive failure', "(2, ['tar', '--delay-directory-restore', '-z', '-x', '--exclude=*/dev/*', '-f', '/tmp/tmpuwlu_of0', '-C', '/tmp/insights-4vu_fepw'], b'tar: insights-client.example.com-20260127130712/data/insights_commands/ls_-lH_.boot.grub.grub.conf_.boot.grub2.grub.cfg_.dev.mapper.vgdata-lvapp_.dev.mapper.vgdata-lvccv_.dev.mapper.vgdata-lvdata_.dev.mapper.vgdata-lvhome_.dev.mapper.vgdata-lvlogs_.dev.mapper.vgdata-lvopt_.dev.mapper.vgsystem-lvroot_.dev.mapper.vgsystem-lvsw: Cannot open: File name too long\\\\ntar: insights-client.example.com-20260127130712/data/insights_commands/ls_-lan_._.boot_.ccv_.dev_.dev.block_.dev.cciss_.dev.disk.by-id_.dev.disk.by-label_.dev.disk.by-path_.dev.disk.by-uuid_.dev.mapper_.dev.oracleasm.disks_.etc_.etc.crypto-policies_.etc.crypto-policies.back-ends_.etc.crypto-policies.state_.etc.dnf.vars_.etc.: Cannot open: File name too long\\\\ntar: Exiting with failure status due to previous errors\\\\n')")
Business Impact
- Systems cannot remain registered to Insights when IOP is enabled.
- Insights functionality is effectively unusable in this setup.
Expected Behavior
After successful "insights-client --register", the system should remain registered and "insights-client --status" should confirm registration via Insights API.
