Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
When remediating a vulnerability through receptor while verifying https://bugzilla.redhat.com/show_bug.cgi?id=1985287, the remediation fails with this in /var/log/insights-client/insights-client.log:
"""
2021-08-06 07:14:22,038 DEBUG insights.client.support Registration status: None
2021-08-06 07:14:22,039 DEBUG insights.client.client System is NOT registered locally via .registered file.
2021-08-06 07:14:22,039 DEBUG insights.client.client Insights API says this machine is NOT registered.
2021-08-06 07:14:22,041 INFO insights.client.client This machine has not yet been registered. Use --register to register this machine.
2021-08-06 07:14:22,044 DEBUG metrics Metrics: authmethod not defined in insights-client config. Defaulting to CERT
2021-08-06 07:14:22,044 DEBUG metrics Metrics: Posting event...
2021-08-06 07:14:22,044 DEBUG metrics Metrics: POST https://cert.cloud.redhat.com:443/api/module-update-router/v1/event
2021-08-06 07:14:22,803 DEBUG metrics Metrics: HTTP Status Code: 201 Created
"""
and this in `journalctl -u "receptor@*"`:
"""
Aug 06 06:53:56 systemd[1]: Started Receptor Node for rh_1212729.
Aug 06 07:14:22 receptor[1183]: ERROR 2021-08-06 07:14:22,854 b18792c5-a51d-45ff-bf85-23d946825300 run Playbook run 8dd6e09d-03bb-4ccf-88e0
Aug 06 07:14:22 receptor[1183]: This machine has not yet been registered. Use --register to register this machine.
Aug 06 07:14:22 receptor[1183]: ', aborting.
"""
Version-Release number of selected component (if applicable):
Satellite 6.10.0 snap 12.0
How reproducible:
Always
Steps to Reproduce:
1. Configure cloud connector, have a remediable host and inventory uploaded
2. On CRC, create a remediation
3. Attempt to apply that remediation
Actual results:
Remediation fails with mentioned messages in logs
Expected results:
Successful remediation
Verified on Satellite 6.10.0 snap 14
The Satellite host is now registered to Insights after running `Configure Cloud Connector`.
Comment 6Lukáš Hellebrandt
2021-09-13 15:38:04 UTC
Sat 6.10.0 snap 18.0:
```
# insights-client --status
System is registered locally via .registered file. Registered at 2021-09-13T10:35:51.226820
Insights API confirms registration.
```
Also, the receptor service is running.
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702