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 2167493 - Remove the setting 'Use remote execution by default'
Summary: Remove the setting 'Use remote execution by default'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.15.0
Assignee: Jeremy Lenz
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-06 19:15 UTC by Jayant Bhatia
Modified: 2024-04-23 17:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:13:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36083 0 Normal Closed Remove the setting 'Use remote execution by default' 2023-09-06 20:11:58 UTC
Red Hat Issue Tracker SAT-15787 0 None None None 2023-02-09 15:48:32 UTC
Red Hat Issue Tracker SAT-15937 0 None None None 2023-02-17 17:05:07 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:13:24 UTC

Description Jayant Bhatia 2023-02-06 19:15:29 UTC 
Description of problem:

The Katello Agent/Goferd has been deprecated and has been replaced by remote execution. The "Satellite WebUI -> Administer -> Settings -> Content -> Use remote execution by default" is by default set to "No". Since Katello Agent/Goferd has been deprecated, this setting should either be set to 'Yes' by default or should be removed.


Version-Release number of selected component (if applicable): satellite-installer-6.13.0.2-1.el8sat.noarch


How reproducible: Always


Steps to Reproduce:
1. Navigate to '"Satellite WebUI -> Administer -> Settings -> Content"'
2. Look for "Use remote execution by default" setting.


Actual results: The "Use remote execution by default" setting is set to "No"


Expected results: The "Use remote execution by default" setting should either be set to 'Yes' by default or should be removed considering katello agent/gofer method has been deprecated.


Additional info: Use remote execution by default -> If this is enabled, remote execution is used instead of katello-agent for remote actions
Comment 1 Ron Lavi 2023-02-12 08:05:26 UTC 
Created redmine issue https://projects.theforeman.org/issues/36083 from this bug
Comment 4 Ron Lavi 2023-02-21 13:47:55 UTC 
As discussed on the PR in https://github.com/Katello/katello/pull/10449#issuecomment-1437088717
We think that this should be postponed and the setting should be removed as part of the upcoming work removing katello-agent,
instead of setting it by default to true.
Comment 6 Jeremy Lenz 2023-03-16 20:37:27 UTC 
Original title: "The 'Use remote execution by default' setting should be set to 'Yes' instead of 'No'"

Updating the title to reflect https://bugzilla.redhat.com/show_bug.cgi?id=2167493#c4
Comment 8 Bryan Kearney 2023-08-09 20:02:35 UTC 
Upstream bug assigned to jlenz
Comment 9 Bryan Kearney 2023-08-09 20:02:37 UTC 
Upstream bug assigned to jlenz
Comment 10 Bryan Kearney 2023-08-18 00:02:36 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36083 has been resolved.
Comment 11 Vladimír Sedmík 2023-09-20 09:24:21 UTC 
Verified the settings were removed from UI, CLI, API in Stream snap 29.0.

[root@satellite ~]# hammer settings info --name remote_execution_by_default
Error: setting not found.
[root@satellite ~]# hammer settings info --name  content_action_accept_timeout
Error: setting not found.
[root@satellite ~]# hammer settings info --name content_action_finish_timeout
Error: setting not found.
Comment 12 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 15 errata-xmlrpc 2024-04-23 17:13:23 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.15.0 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-2024:2010
Note You need to log in before you can comment on or make changes to this bug.