Actions
Bug #38468
closedUnable to run a rex job after rebuilding of a provisioned host
Difficulty:
Triaged:
Yes
Description
Description of problem:
Unable to run a rex job after rebuilding of a provisioned host
How reproducible:
100%
Is this issue a regression from an earlier version:
No
Steps to Reproduce:
Provision a host
Run a rex job (set Connect by IP to Yes)
Rebuild the host
Try running a 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
Additional notes:
It seems that rebuilding a host in-place doesn't reset the host-proxy mapping in host_proxy_invocations.
Updated by The Foreman Bot 23 days ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/976 added
Updated by The Foreman Bot 12 days ago
- Fixed in Releases foreman_remote_execution-16.0.3 added
Updated by Adam Lazik 12 days ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_plugin|23ae2cbe594f50a0886891c2ab593ef135e77638.
Actions