Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 1467761 - [RFE] Script should help create ssh key and copy it to the remote libvirt host
Summary: [RFE] Script should help create ssh key and copy it to the remote libvirt host
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Kunxin Huang
satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-05 03:39 UTC by Eko
Modified: 2020-10-21 13:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 13:46:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20261 0 Normal New Script should help create ssh key and copy it to the remote libvirt host 2020-10-21 13:35:48 UTC

Description Eko 2017-07-05 03:39:03 UTC
for remote libvirt mode, virt-who only support to run by ssh key, don't support by username and password, 

so I suggest the script helps to create the ssh key and then upload it to the remote libvirt by auto.

Comment 2 Marek Hulan 2017-07-10 13:40:22 UTC
And it could be even integrated with SSH keys uploaded to user. The problem I see is that the script would need to ssh to the host which would make it interactive. Maybe that could be a different script or hammer command to run. It should probably also be able to do ssh-keygen if user decides to generate a new key.

Comment 3 Marek Hulan 2017-07-10 13:42:15 UTC
Created redmine issue http://projects.theforeman.org/issues/20261 from this bug

Comment 4 Marek Hulan 2017-07-10 13:43:04 UTC
Or the installation could be done through REX once it supports password based authentication.

Comment 5 Bryan Kearney 2019-02-07 12:09:39 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 6 Marek Hulan 2019-02-11 09:50:55 UTC
Password can be now specified, users can create REX job for setting up ssh key. It can download it from Capsule API since public key is exposed there.

Comment 7 Sean O'Keeffe 2020-10-21 13:46:55 UTC
The RFE triage team have evaluated this request, and while it's a valid request, we are closing this as it isn't being prioritized to fix in the next several releases.
If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support.
Thank you


Note You need to log in before you can comment on or make changes to this bug.