-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
False
-
sat-proton
-
Known Issue
-
-
None
-
None
Description of problem:
insights-client errors on hosts registered to Satellite after disabling or re-enabling IoP on the Satellite.
How reproducible:
100%
Is this issue a regression from an earlier version:
Steps to Reproduce:
1. Satellite: disable IoP
# satellite-installer --iop-ensure absent
2. Client sees error reaching hosted Insights/Lightspeed API through Satellite
# insights-client --status System is registered locally via .registered file. Registered at 2025-12-01T18:45:53.889637 Insights API could not be reached to confirm registration status.
- Satellite: restart foreman service
# systemctl restart foreman
- Client can now successfully verify status
# insights-client --status System is registered locally via .registered file. Registered at 2025-12-01T18:45:53.889637 Insights API says this machine is NOT registered. System unregistered locally via .unregistered file
- Satellite: re-enable IoP
# satellite-installer --iop-ensure present
- Client can re-register, but it fails when uploading its inventory to Satellite:
# insights-client --status System is NOT registered locally via .registered file. Unregistered at 2025-12-01T18:58:05.699418 Insights API says this machine is NOT registered. System unregistered locally via .unregistered file # insights-client --register Successfully registered host host1.example.com Automatic scheduling for Insights has been enabled. Starting to collect Insights data for host host1.example.com Writing RHSM facts to /etc/rhsm/facts/insights-client.facts ... Uploading Insights data. Upload archive failed with status code 502 Upload attempt 1 of 1 failed! Reason: 502: Bad Gateway All attempts to upload have failed! Please see /var/log/insights-client/insights-client.log for additional information Upload failed. # insights-client --status System is registered locally via .registered file. Registered at 2025-12-01T19:03:06.582968 Insights API could not be reached to confirm registration status.
- Satellite: restart foreman again
# systemctl restart foreman
- Client: inventory upload now works again
# insights-client Starting to collect Insights data for host host1.example.com Writing RHSM facts to /etc/rhsm/facts/insights-client.facts ... Uploading Insights data. Successfully uploaded report for host host1.example.com. View details about this system on console.redhat.com: https://console.redhat.com/insights/inventory/7d8a0551-69be-4d12-8943-267727de092a
Actual behavior:
Manual foreman service restart required after IoP is disabled or re-enabled
Expected behavior:
No manual restarts required after running satellite-installer --iop-ensure (absent|present) to turn off or re-enable IoP.
Business Impact / Additional info:
- duplicates
-
-
- New
-