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
We have been working on generating an ansible role based on the current kdump configuration in Cockpit and noticed that with an ssh target kdump_ssh_user and kdump_ssh_server while they could be found out from the kdump location.
Without it the role fails.
localhost | SUCCESS | rc=0 >>
skipped, since /root/.ssh/id_rsa existsDid not run command since '/root/.ssh/id_rsa' exists
localhost | SUCCESS => {
"changed": false,
"encoding": "base64",
"source": "/root/.ssh/id_rsa.pub"
}
localhost | FAILED! => {
"changed": false,
"msg": "argument 'name' is of type <class 'NoneType'> and we were unable to convert to str: 'None' is not a string and conversion is not allowed"
}
I couldn't find any documentation on kdump_ssh_user and kdump_ssh_server do the exist to copy the ssh key to the configured kdump user in the kdump location so that you could have a special kdump user to write the dump too?
The text was updated successfully, but these errors were encountered:
We uncovered an issue when we don't provide a username and set the location to example.com but do set kdump_ssh_server and kdump_ssh_user. This would lead to a kdump.conf with
See https://bugzilla.redhat.com/show_bug.cgi?id=2251216 for the kexec-tools side of this -- but I suspect they don't actually want to accept ssh hostname, and it's just giving a bad error message. I think it'd be preferable in this case to only specify kdump_ssh_{server,user} and not kdump_target.location -- that will both fix the redundancy and also avoid that kexec-tools bug.
We have been working on generating an ansible role based on the current kdump configuration in Cockpit and noticed that with an ssh target
kdump_ssh_user
andkdump_ssh_server
while they could be found out from the kdump location.Without it the role fails.
I couldn't find any documentation on
kdump_ssh_user
andkdump_ssh_server
do the exist to copy the ssh key to the configured kdump user in the kdump location so that you could have a special kdump user to write the dump too?The text was updated successfully, but these errors were encountered: