RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

* Add the target ssh host key to known_hosts on the managed hosts

When using ssh for kdump, the ssh host key of the target host needs to be added to known_hosts on the managed hosts.  Otherwise, ssh may not work.

* Set a default kdump_target.location for ssh

If using ssh, and kdump_target.location is not set, default the dump location to kdump_ssh_user@kdump_ssh_server

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I believe the patch for this has been there for a long time (if this is just about PR 22 and nothing else, this PR has a patch downstream) and the problem that it solves was originally reported as bz1651342 (and in RHEL 8 fixed together with bz1664757). Can I close it as duplicate or CURRENTRELEASE?

(In reply to Pavel Cahyna from comment #1)
> I believe the patch for this has been there for a long time (if this is just
> about PR 22 and nothing else, this PR has a patch downstream) and the
> problem that it solves was originally reported as bz1651342 (and in RHEL 8
> fixed together with bz1664757). Can I close it as duplicate or
> CURRENTRELEASE?

Ah, I see - this is rhel-system-roles-kdump-pr22.diff - so yes, let's close this bz