Remote Execution not being used despite being set as default
Administer > Settings > Content :
Use remote execution by default: YES
With the above setting, the default action (install package, update errata) is still trying to use katello-agent, and tasks are failing (as katello-agent is not installed).
Select a content host and navigate to Packages > Installed
Search for packages (e.g. ‘iwl1000’) and click ‘Remove Selected’ after selecting package.
Nothing will happen on the host
Expected actions to use Remote Execution over katello-agent
Foreman and Proxy versions:
Attached logs are referenced in https://community.theforeman.org/t/remote-execution-not-being-used-despite-being-set-as-default/15103/2
- Fixes #27714 - Generate bastion config on load
This commit adds a config generator option to bastion so that it reloads
the configurations on every page load. Prior to this commit the plugins
were returning a static list of config items, which means if some one
changed "remote_execution_by_default" setting, the config would not get
regenerated in the UI.
Also updated the content-host installed packages controller to handle
removal by both katello-agent and remote action
Also includes a bunch of unit tests.