Bug #31894
closedApplying errata from the errata's page always tries to use katello-agent even when remote_execution_by_default set to true
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1898367
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):
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:
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/9175 added
Updated by John Mitsch almost 4 years ago
- Subject changed from Applying errata from the errata's page always tries to use katello-agent even when remote_execution_by_default set to true to Applying errata from the errata's page always tries to use katello-agent even when remote_execution_by_default set to true
- Target version set to Katello 4.1.0
- Triaged changed from No to Yes
Updated by The Foreman Bot almost 4 years ago
- Fixed in Releases Katello 4.1.0 added
Updated by Anonymous almost 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|6d32fc732b4ef436ff979b358577425327b05e9d.