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.

Bug 1861422

Summary: Error encountered while handling the response, replying with an error message ('plugin_config')
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: RH Cloud - Cloud ConnectorAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: aruzicka, ehelms, jyejare, zhunting
Target Milestone: 6.8.0Keywords: Regression, TestBlocker, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python3-receptor-satellite-1.1.1, tfm-rubygem-foreman_remote_execution-3.3.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:04:48 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: 1835882    
Attachments:
Description Flags
foreman-tail.log none

Description Lukáš Hellebrandt 2020-07-28 15:05:54 UTC
Created attachment 1702673 [details]
foreman-tail.log

Description of problem:
I have a Satellite registered as a Source against c.rh.c. When I try to apply a remediation to a Host through this Satellite, I get the attached error message in logs and the remediation is never applied. Note that the Status of Source/Satellite is Unknown in c.rh.c for some reason (not sure if related).

Version-Release number of selected component (if applicable):
Sat 6.8 snap 2.0

How reproducible:
Deterministic

Steps to Reproduce:
Try to apply a remediation using Receptor on Sat 6.8 while tailing logs.

Actual results:
Error, remediation not applied.

Expected results:
Remediation applied.

Comment 4 errata-xmlrpc 2020-10-27 13:04:48 UTC
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 (Important: Satellite 6.8 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-2020:4366