Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update foreman to 3.2.1 #585

Merged
merged 29 commits into from
Jul 19, 2022
Merged

update foreman to 3.2.1 #585

merged 29 commits into from
Jul 19, 2022

Conversation

@jhoblitt
Copy link
Member Author

jhoblitt commented Jul 7, 2022

There are live hosts on this branch -- please let me do the merge.

The foreman remote_execution plugin is already installed.
The foreman tasks plugin is already installed.
To pickup fix for client_match_block.
When the ssh client is configured to for sssd/ipa host key
tracking using `/usr/bin/sss_ssh_knownhostsproxy` as a `ProxyCommand`,
this somehow breaks foreman-proxy REX.  Without a valid shell set in
`/etc/passwd` or via the `SHELL` env var, the ssh client errors claiming
there is a key exchange failure but never gets as far as opening a
network socket.  With a valid `SHELL`, ssh sessions are able to be
established but it appears that no stdout/stderr is piped back to the
foreman-proxy daemon.  The only identified work around is remove the
`ProxyCommand` completely for the `foreman-proxy` user.

There is some discussion of this problem on
theforeman/puppet-foreman_proxy#742
This is desired to simply manual deletion of templates.
To prevent the ssh client from hanging when connecting to github.com for
the first time.
This is necessary to allow foreman to ssh to libvirt compute resources
without using /usr/bin/sss_ssh_knownhostsproxy.
@jhoblitt jhoblitt merged commit aff2ebd into master Jul 19, 2022
@jhoblitt jhoblitt deleted the IT-3497/foreman3 branch July 19, 2022 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants