Problem:
Our hosts are provisioned by our infrastructure team and then registered into Foreman.
When a host registered in Foreman is redeployed, its host key changes but the old key is still registered in foreman-proxy user’s known_hosts file.
This produces an error when Foreman tries to access the host, e.g remote execution:
Error initializing command: Net::SSH::HostKeyMismatch - fingerprint ba:19:05:e4:37:80:53:66:57:41:61:ff:97:04:64:32 does not match for “XX.X.X.XX”
What would be a recommended way to handle this ?
Foreman and Proxy versions: 3.17