Skip to content

Commit

Permalink
Add RN for yggdrasil
Browse files Browse the repository at this point in the history
  • Loading branch information
asteflova committed Jan 17, 2025
1 parent 60efa1c commit 1a962b8
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion guides/doc-Release_Notes/topics/foreman.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,11 @@
[id="foreman-headline-features"]
== Headline Features

There are no highlights with Foreman {ProjectVersion}.
=== Remote execution in pull mode is now compatible with clients running `yggdrasil` versions 0.2.z and 0.4.z

The remote execution pull provider has been updated to be compatible with all versions of the `yggdrasil` package that can be installed on a host. As a result, remote execution jobs in pull mode work on Foreman hosts that run any of the currently supported versions of EL. This applies also to hosts with the Extra Packages for Enterprise Linux (EPEL) repository enabled.

The pull-based transport mode relies on the Yggdrasil service and requires different Yggdrasil configuration based on the version of the `yggdrasil` package that is installed on the host. If weak dependencies are enabled on your hosts, the Yggdrasil client configuration is automatically updated and no further steps are required. If weak dependencies are disabled on your hosts, you must install the `foreman_ygg_migration` package manually to ensure that the Yggdrasil client configuration is updated. For detailed instructions, see link:https://docs.theforeman.org/3.14/Managing_Hosts/index-katello.html#troubleshooting-remote-jobs-timing-out-after-yggdrasil-update[Troubleshooting: Remote jobs timing out after yggdrasil update] in _{ManagingHostsDocTitle}_.

[id="foreman-upgrade-warnings"]
== Upgrade Warnings
Expand Down

0 comments on commit 1a962b8

Please sign in to comment.