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?
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_userandkdump_ssh_serverwhile they could be found out from the kdump location.Without it the role fails.
I couldn't find any documentation on
kdump_ssh_userandkdump_ssh_serverdo 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?