Problem:
Not really a problem, just wondering that, if katello-agent is replaced by remote execution, can apply errata the same way as before? ex: "content–>errata → box errata ID and apply to all hosts.
Expected outcome:
Apply erratas or packages to several batches of hosts
I already setup a guest with ssh keys exchange (waiting on network side to try it out).
Is it expected that after port 22 is opened between Foreman and guest, erratas and packages can be applied?
Can you let me know if my current setup is up-to-date and adequate for these tasks?
Yes katello-agent is being depreciated and remote execution is now the default. It can do all the things that katello-agent can do so you should be good to go. The installer command you ran turns it on so I will mark this one as solved.
thanks for the reply. Sure mark it as solved.
From my setup would you say I am good to go for the upcoming time?
Also as a rookie with foreman-katello, the execution to enable the plugins was the correct right? (Previous post). Thanks and cheers
I think you are good to go for the upcoming future. Yeah by default with Katello we enable the Remote Execution feature so we can associate the templates etc. The next step is what you did allows the smart proxy to ssh to the clients to perform the job you select.
Can it be that katello-agent is running on the background here and remote execution only on scheduled tasks?
Any way to pick up the errata collection in content and apply it?
The last setting in the list should be “Use remote execution by default”. Set that to “Yes” to use remote execution instead of katello agent by default.
What you hit will be fixed in the next release with better logic around if katello-agent/rex are enabled.
In the interim, can you goto Settings, Content and change Use remote execution by default to true and try again. Also if that does not work there should be a dropdown button, select that and use remote execution.