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.
DescriptionJoniel Pasqualetto
2020-11-16 21:15:37 UTC
Description of problem:
Option "remote_execution_by_default" is set to true:
~~~
# hammer settings list |grep remote_execution_by_default
remote_execution_by_default | Use remote execution by default | true | If set to true, use the remote execution over katello-agent for remote actions
~~~
Going to WebUI > Content > Errata > select errata > apply errata > select a host > Next > Apply Errata > Confirm tries to use katello-agent and not remote execution.
Version-Release number of selected component (if applicable):
Satellite 6.7
How reproducible:
Always
Steps to Reproduce:
1. Set option remote_execution_by_default to true:
hammer settings set --name remote_execution_by_default --value true
2. Go to the WebUI > Content > Errata > select errata > apply errata > select a host > Next > Apply Errata > Confirm
Actual results:
Satellite tries to push the errata installation using katello-agent
Expected results:
Satellite should use remote execution to push the errata installation
Additional info:
The fix for this was in upstream Katello 3.14. Since Satellite 6.9 is based upon Katello 3.18, it should be included there as well. Updating release and state so that it may go through verification.
Comment 5Tasos Papaioannou
2021-02-02 16:24:33 UTC
Tested on 6.9.0 snap 11.0. I still see the same behavior:
With remote execution enabled on the content host, errata updates are successful when scheduled either from the content host's Errata tab or from the list of Content Hosts, if I select "via remote execution" as the method.
When scheduled from the Content > Errata page, however, the task fails with 'Host did not respond within 20 seconds. The task has been cancelled. Is katello-agent installed and goferd running on the Host?' The same behavior occurs regardless of whether remote_execution_by_default is set to true or false.
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