Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
The virt-who documentation at https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/virtual-instances-guide/chapter-5-configuration-and-services say:
"In the Satellite web UI, create a user on the Satellite Server with Administrator access."

This does seem to be the case, creating a user with create_hosts/content_hosts & edit_hosts/content_hosts gives permission denied errors. This is stupid and insecure, we should allow this to work with the permissions above or create a new virt-who permission that works.

It would also be nice ship Satellite with a per-definded role for virt-who

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

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
the Virt-who satellite user requires admin rights 


Expected results:
virt-who user does require admin rights


Additional info:

I've just tested this on katello nightly and cannot reproduce it anymore. All that is required it the user has "create_hosts" permission. I'm also fairly sure this will have has been fixed in 6.3, could someone test that please? 

Moving to Doc bug.

It looks like this is no longer a bug, as https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html-single/virtual_instances_guide/index#authentication_requirements says "Every virt-who configuration, created using either the Satellite web UI or hammer, creates a unique service user for virt-who authentication. The user is named virt_who_reporter$id and has a randomly generated password. The virt-who user is assigned the Virt-who Reporter role, which provides minimal permissions, allowing the user to only perform virt-who reporting."

If there are any issues with the current authentication information, however, please do let us know.