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:
Nowadays many customers use virt-who reporting tool associated with their hypervisors. This tool is reporting the data through network and needs access to the satellite server. To accomplish this, the customer has to create an user and assign it some role. Or better, create role with limited privileges and then an user assigned with that role.
Version-Release number of selected component (if applicable):
6.2.x
Recommendation:
Create default role which will have assigned all required permissions, which should be these:
Resource | Permissions
--------------------- | ----------------------------------------
Host | create_hosts, edit_hosts
Content Host | create_content_hosts, edit_content_hosts
Miscellaneous | my_organizations
Lifecycle Environment | view_lifecycle_environments
Also we can have virt-who user created by default, which should be disabled and with some random password, so user will be at least forced to enable the user and give it some password.
Comment 3sthirugn@redhat.com
2017-04-18 15:03:37 UTC
This will be delivered with Satellite 6.3 as part of the foreman_virt_who_configure plugin.
VERIFIED
Version tested:
Satellite 6.3 Snap 13
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.3-1.el7sat.noarch
tfm-rubygem-foreman_virt_who_configure-0.1.5-1.fm1_15.el7sat.noarch
[root@sat63-qa-rhel7 ~]# hammer role list |grep -i "virt-who"
16 | Virt-who Manager | no
15 | Virt-who Reporter | no
17 | Virt-who Viewer | no
[root@sat63-qa-rhel7 ~]# hammer role filters --name "Virt-who Manager"
----|---------------------------------|--------|------------|-----------|------------------|---------------------------------------------------------------------------------
ID | RESOURCE TYPE | SEARCH | UNLIMITED? | OVERRIDE? | ROLE | PERMISSIONS
----|---------------------------------|--------|------------|-----------|------------------|---------------------------------------------------------------------------------
212 | ForemanVirtWhoConfigure::Config | none | yes | no | Virt-who Manager | view_virt_who_config, create_virt_who_config, edit_virt_who_config, destroy_v...
----|---------------------------------|--------|------------|-----------|------------------|---------------------------------------------------------------------------------
[root@sat63-qa-rhel7 ~]# hammer role filters --name "Virt-who Reporter"
----|------------------------|--------|------------|-----------|-------------------|----------------------------
ID | RESOURCE TYPE | SEARCH | UNLIMITED? | OVERRIDE? | ROLE | PERMISSIONS
----|------------------------|--------|------------|-----------|-------------------|----------------------------
209 | Host | none | yes | no | Virt-who Reporter | create_hosts, edit_hosts
210 | Katello::KTEnvironment | none | yes | no | Virt-who Reporter | view_lifecycle_environments
211 | (Miscellaneous) | none | yes | no | Virt-who Reporter | my_organizations
----|------------------------|--------|------------|-----------|-------------------|----------------------------
[root@sat63-qa-rhel7 ~]# hammer role filters --name "Virt-who Viewer"
----|---------------------------------|--------|------------|-----------|-----------------|---------------------
ID | RESOURCE TYPE | SEARCH | UNLIMITED? | OVERRIDE? | ROLE | PERMISSIONS
----|---------------------------------|--------|------------|-----------|-----------------|---------------------
213 | ForemanVirtWhoConfigure::Config | none | yes | no | Virt-who Viewer | view_virt_who_config
----|---------------------------------|--------|------------|-----------|-----------------|---------------------
Comment 9Satellite Program
2018-02-21 16:51:07 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
>
> For information on the advisory, and where to find the updated files, follow the link below.
>
> If the solution does not work for you, open a new bug report.
>
> https://access.redhat.com/errata/RHSA-2018:0336