You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally we encounter these, while I understand the issue, I am not sure how we encounter them but given how our automation is behind a firewall on secure servers , its probably best we have the tool automatically react to this and correct it without user intervention.
The output has been sanitized with ec12345a.sanitized.host.ibm.com
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:JE+Fv4b8YJgBx/PQ0+I0/pEnGkiUommL0RPRXI3B7KI.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:47
Host key for ec12345a.sanitized.host.ibm.com has changed and you have requested strict checking.
Host key verification failed.
I see two options, the AC tool read and grep the responses and then to forcibly correct it with either:
ssh-keygen -R [IP_ADDRESS]
or where 47d is the offending key line number reported Offending ECDSA key in /root/.ssh/known_hosts:47
sed -i -e 47d /root/.ssh/known_hosts
Ansible module
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Enabler description
Occasionally we encounter these, while I understand the issue, I am not sure how we encounter them but given how our automation is behind a firewall on secure servers , its probably best we have the tool automatically react to this and correct it without user intervention.
The output has been sanitized with
ec12345a.sanitized.host.ibm.com
I see two options, the AC tool read and grep the responses and then to forcibly correct it with either:
or where
47d
is the offending key line number reportedOffending ECDSA key in /root/.ssh/known_hosts:47
Ansible module
No response
The text was updated successfully, but these errors were encountered: