Bug 1898367

Summary:	Applying errata from the errata's page always tries to use katello-agent even when remote_execution_by_default set to true
Product:	Red Hat Satellite	Reporter:	Joniel Pasqualetto <jpasqual>
Component:	Errata Management	Assignee:	Ian Ballou <iballou>
Status:	CLOSED ERRATA	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.7.0	CC:	gpadholi, iballou, jjeffers, kagarwal, kupadhya, mkalyat, swadeley, zhunting
Target Milestone:	6.9.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.18.1.7-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1943260 (view as bug list)		Environment:
Last Closed:	2021-04-21 13:18:55 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:

Description Joniel 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:

Comment 1 Bryan Kearney 2020-12-16 19:30:33 UTC

Upstream bug assigned to paji

Comment 2 Bryan Kearney 2020-12-16 19:30:34 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/27714 has been resolved.

Comment 3 Brad Buckingham 2021-01-08 22:09:30 UTC

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 5 Tasos 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.

Comment 6 Ian Ballou 2021-02-16 15:46:29 UTC

Created redmine issue https://projects.theforeman.org/issues/31894 from this bug

Comment 8 Tasos Papaioannou 2021-03-03 21:37:10 UTC

Verified on 6.9.0 snap 15.0.

Comment 12 errata-xmlrpc 2021-04-21 13:18:55 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 (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