Bug #38425
open
Unable to run a rex job when a provisioned host is deleted and created again with same IP address
Description
Description of problem:
When the connect_by_ip setting is set to yes, Foreman is unable to run a rex job when a provisioned host is deleted and created again with same IP address
How reproducible:
100%
Steps to Reproduce:
1. Provision a host
2. Run a rex job (set Connect by IP to yes)
3. Delete the host and create a new host(give same IP to the host as of the first provisioned host)
4. Try running a rex job again
Alternative steps to reproduce
1. Have the setting connect_by_ip set to yes
2. Register a host to Foreman
3. Run a REX job
4. Delete the host from Foreman
5. On the host run: `rm -f /etc/ssh/ssh_host_* && ssh-keygen -A && systemctl restart sshd && <registration command with force=true>`
6. Run the REX job again
Actual behavior:
The rex job fails on the host.
The job error is `Offending ED25519 key in /usr/share/foreman-proxy/.ssh/known_hosts:1`
Expected behavior:
The rex job should pass
Updated by The Foreman Bot 1 day ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/125 added