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.
DescriptionLukáš Hellebrandt
2020-10-01 12:27:54 UTC
Created attachment 1718161[details]
0-failure.log
Description of problem:
receptor-satellite allows inconsistent combination of status codes. There are the following codes in the message from receptor to c.rh.c:
satellite_connection_code (set wrong password in receptor.conf): 0 if connection between Receptor and Satellite is successful, non-zero otherwise
connection_code (delete foreman-proxy's ssh key from host's authorized_keys): 0 if connection between Satellite and the host is successful, non-zero otherwise
execution_code (change binary used in remediation to 'exit 1'): 0 if playbook finished successfully, non-zero otherwise
satellite_infrastructure_code (not tested): should return 0 when connection between satellite and connection is successful, non-zero otherwise
The one weird thing I encountered during testing is that if connection between Receptor and Satellite fails (I actually set wrong password in receptor.conf), then satellite_connection_code!=0 and connection_code==0. Connection between Satellite and host could, however, never have succeeded because Satellite wasn't instructed to do anything in the first place. Log of this case attached.
It doesn't make much sense to me, in combination with status==failure. Also, c.rh.c team confirmed they would prefer something that is more consistent, like connection_code==null.
Version-Release number of selected component (if applicable):
Sat 6.8. Not a regression - not supported in previous versions.
How reproducible:
Deterministic
Steps to Reproduce:
1. Setup receptor and host, upload inventory
2. Create remediation
3. Set wrong password in receptor.conf
4. Try to apply the remediation
Actual results:
Error, satellite_connection_code!=0 and connection_code==0
Expected results:
Error, satellite_connection_code!=0 and connection_code==null
Verified
On Sat 6.9 snap 18
Tested a successful remediation: All codes were 0.
Set wrong password in receptor.conf: satellite_connection_code = 1; connection_code = null; execution_code = null
Disabled authentication of ssh between satellite and host: satellite_connection_code = 0; connection_code = 1; execution_code = null
Made sure the remediation playbook would fail on host: satellite_connection_code = 0; connection_code = 0; execution_code = 2
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.9 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:1313
Created attachment 1718161 [details] 0-failure.log Description of problem: receptor-satellite allows inconsistent combination of status codes. There are the following codes in the message from receptor to c.rh.c: satellite_connection_code (set wrong password in receptor.conf): 0 if connection between Receptor and Satellite is successful, non-zero otherwise connection_code (delete foreman-proxy's ssh key from host's authorized_keys): 0 if connection between Satellite and the host is successful, non-zero otherwise execution_code (change binary used in remediation to 'exit 1'): 0 if playbook finished successfully, non-zero otherwise satellite_infrastructure_code (not tested): should return 0 when connection between satellite and connection is successful, non-zero otherwise The one weird thing I encountered during testing is that if connection between Receptor and Satellite fails (I actually set wrong password in receptor.conf), then satellite_connection_code!=0 and connection_code==0. Connection between Satellite and host could, however, never have succeeded because Satellite wasn't instructed to do anything in the first place. Log of this case attached. It doesn't make much sense to me, in combination with status==failure. Also, c.rh.c team confirmed they would prefer something that is more consistent, like connection_code==null. Version-Release number of selected component (if applicable): Sat 6.8. Not a regression - not supported in previous versions. How reproducible: Deterministic Steps to Reproduce: 1. Setup receptor and host, upload inventory 2. Create remediation 3. Set wrong password in receptor.conf 4. Try to apply the remediation Actual results: Error, satellite_connection_code!=0 and connection_code==0 Expected results: Error, satellite_connection_code!=0 and connection_code==null