Bug 2213634

Summary:	[DDF] If you choose not to use the hypervisor password for libvirt, set up SSH public key authentication from the
Product:	Red Hat Satellite	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Virt-who Configure Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	yanpliu <yanpliu>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	6.13.0	CC:	bangelic, chrobert, lufu, mdolezel
Target Milestone:	Unspecified	Keywords:	Documentation, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:21:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-06-08 19:39:17 UTC

If you choose not to use the hypervisor password  for libvirt, set up SSH public key authentication from the system that is running virt-who to the hypervisor with your virt-who user (https://access.redhat.com/solutions/4110681)

Reported by: calvin

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/configuring_virtual_machine_subscriptions_in_red_hat_satellite/creating-a-virt-who-configuration_vm-subs-satellite#annotations:eaf71c04-8ea4-4e56-8576-5fe7d27cd655

Comment 2 Marie Hornickova 2023-06-09 10:59:09 UTC

Hello,
Many thanks for using the Direct Documentation Feedback tool to report this suggestion for improvement.

Information about the updates regarding its implementation will be shared here.

Thank you!

Comment 7 Eric Helms 2024-06-06 16:21:40 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 8 Red Hat Bugzilla 2024-10-05 04:26:14 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days