Project

General

Profile

Actions
Copy link

Bug #31894

closed

Applying errata from the errata's page always tries to use katello-agent even when remote_execution_by_default set to true

Added by Ian Ballou over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Ian Ballou
Category:
Errata Management
Target version:
Katello 4.1.0
Difficulty:
Triaged:
Yes
Bugzilla link:
1898367
Pull request:
https://github.com/Katello/katello/pull/9175
Fixed in Releases:
Katello 4.1.0
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1898367

Description of problem:

Option "remote_execution_by_default" is set to true:

~~~
  1. 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):
Katello 3.14

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:
Katello tries to push the errata installation using katello-agent

Expected results:
Katello should use remote execution to push the errata installation

Additional info:

Actions
Copy link

Also available in: Atom PDF